Hello.

I am new to OMV5 and this forum.

I have installed it on an raspberry pi 4 and everything worked.

Then I wanted to expose it to the internet and of course over SSL!

I already have an DuckDNS account for my home assistant installation that runs over SSL on the same raspberry using docker...

This is what I did:

I installed letsencrypt docker container using docker-compose with my duckdns account and token.

Ports I have used are 4443->443 and 81->80.

On my router I forwarded 443->4443 and 80->81

The generated key and cert file I have copy and paste to the OMV5 config.

Everything worked fine.

Then I have gone to the Settings and switched to SSL over Port 443 in OMV5.

After half a minute OMV showed an error, which is correct as I think, because the OMV5 GUI is not available on port 80 any more.

Now I am not able anymore to access the GUI

Even on port 80, even though I did not choose to force SSL connection.

I could help myself by using omv-firstaid and reset the WEB UI to port 80.

Now my question is... How can I forward my https Connection over DuckDNS to my OMV?

If I go to https://xxxxxx.duckdns.org it only shows me:

-------------------------------------------------------------------------

Welcome to our server

The website is currently being setup under this address.

For help and support, please contact: me@example.com

-------------------------------------------------------------------------

what tells me, that the https connection to my raspberry is up and running.

Could someone of you help me with this, please?

Okay. I am new to this.

Remote access to the GUI is not really necessary, that’s right.

But in the config of OMV I can choose access the GUI over https.

But it doesn’t work...

Edit: I got it working now!!

Even if I don’t really need to access the GUi over the internet, it would be great if I can access my Files on the NAS over the Internet.

Perhaps I am on the wrong path.

How do you get your data accessible online?

Is nextcloud the way I should lookout for?

Hmmm. I think nextcloud is overpowered if I only want to access my filesystem from the internet.

If I would use nextcloud, can I simply link my folders on my HDD to be accessible over the cloud?

And the installation will be not so easy, I think, because I am using Home Assistant on the same server and I have several docker containers using the required ports.

Deconz is using 443, NGINX Reverse Proxy for HA is using 444, OMV5 is using 446 for https access with DuckDNS SSL.

Perhaps I can use SFTP to access files over the internet?

Big thanks, macom !

I think installing nextcloud will offer me the most comfort together with the remote storage app.

443 and 80 are externally in use to access the OMV WebGUI over https.

I don’t know, if this still work if I change port 80.

443 should be no problem to change to 4443 for example, but I think NGINX needs port 80 for requests?

Hey macom

I need your help, please.

I tried to install NextCloud and I've got the following error from swag.

P.S. : I use port 446 as shown in the log with OMV... and, it works! I forwarded 446 to 446 and I can access OMV.

For HomeAssistant I use port forwarding 8123 to my NGINX reverse proxy at 444. Works, too.

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing... 
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing... 
Variables set:
PUID=1000
PGID=100
TZ=Europe/Berlin
URL=xxxxxxxxxx.duckdns.org
SUBDOMAINS=www,
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=http
DNSPLUGIN=
EMAIL=xxx.xxx@xxx.de
STAGING=
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Sub-domains processed are:  -d www.xxxxxxxxxxx.duckdns.org
E-mail address entered: xxx.xxx@xxx.de
http validation is selected
Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Account registered.
Requesting a certificate for xxxxxxxxxxx.duckdns.org and www.xxxxxxxxxx.duckdns.org
Performing the following challenges:
http-01 challenge for xxxxxxxx.duckdns.org
http-01 challenge for www.xxxxxxxxxxx.duckdns.org
Waiting for verification...
Challenge failed for domain xxxxxxxxxxx.duckdns.org
Challenge failed for domain www.xxxxxxxxxxx.duckdns.org
http-01 challenge for xxxxxxxxxxx.duckdns.org
http-01 challenge for www.xxxxxxxxxxxxxxx.duckdns.org
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
 - The following errors were reported by the server:
   Domain: xxxxxxxxxxxxx.duckdns.org
   Type:   connection
   Detail: Fetching
   https://xxxxxxxxxxx.duckdns.org:446/.well-known/acme-challenge/xxxxxxxxxxxxx:
   Invalid port in redirect target. Only ports 80 and 443 are
   supported, not 446
   Domain: www.xxxxxxxxxxxx.duckdns.org
   Type:   connection
   Detail: Fetching
   https://www.xxxxxxxxxxxx.duckdns.org:446/.well-known/acme-challenge/xxxxxxxxxxxxxxxx:
   Invalid port in redirect target. Only ports 80 and 443 are
   supported, not 446
   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

I got it up and running!!

I have changed the swag part in the compose file to:

swag:
    image: linuxserver/letsencrypt
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - URL=xxxxxx.duckdns.org
      - SUBDOMAINS=www,
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=xxxxxx
      - EMAIL=xxx.xxx@xxx.de
    volumes:
      - /srv/appdata/swag:/config
    ports:
      - 448:443
    restart: unless-stopped

After that it was still not working, because there was this error in swag log

nginx: [emerg] "proxy_max_temp_file_size" directive invalid value in /config/nginx/proxy-confs/nextcloud.subfolder.conf:36

I've edited the file and simply put a # in front of "proxy_max_temp_file_size".

After a restart of swag and nextcloud everything was working fine!!

After some testing I think nextcloud with external storage was the best solution.

That’s great. Big thanks again!