Locked out of OMV5 after setting connection to Port 81, and ongoing SSL/TLS connection issue

Alright so my OMV5 NAS does not connect via HTTPS. It only connected via HTTP, even if I try to force a TLS/SSL connection. I can access the Control Panel, and even network shares where I store my files (via Windows 10 network shares)

My inability to connect via HTTPS (TLS/SSL) only became a problem when I was trying to install "NextCloud". Its an application that allows you to access files remotely on the internet. This video shows you how to do it as a container in Docker, managed by the application Portainer:

Skip to 8:00 to 9:00, and he will talk about running some custom code that he made which will basically set up your NextCloud containers.

However - when you run this guy's code it also requires an encrypted connection, because it sets up something called "NextCloud-LetsEncrypt". This obviously requires that TLS/SSL is enabled on the server for it to work. If you don't have that turned on, then running the code will install the NextCloud application, but not the LetsEncrypt container, and that's a problem

After some troubleshooting - I figured out how to get it working. I turned off SSL/TLS in OMV5 General Settings, but kept TLS/SSL on in the TLS tab. Then I ran the code on more time, and it worked! All the containers were installed.

But... I was having trouble with setting up a "fresh" install of NextCloud - so I decided to start from scratch, reinstall everything etc. make it so I could configure NextCloud properly...

Following his instructions, in General Settings I made my server connect to a different port than HTTP. I set it to Port 81. Then I turned back on TLS/SSL in General Settings....

Now I try to connect using my internal IP, so it looks like this (including the port number):

192.168.1.103:81

Now here is the problem:

1) Using https://192.168.1.103:81

I can't connect to the OMV5 control panel using HTTPS, because it says it "refused to connect". As if it is forcing a TLS/SSL connection...

2) Using http://192.168.1.103:81

I can't connect using HTTP either - it gives the same error.

Did I mess it up? I feel like doing either HTTPS or HTTP at Port 81 wont work.

Furthermore even if I get this working and I get back in - how DO I enable a TLS/SSL connection?

I ultimately want to be able to complete this guy's video and do a proper NextCloud install. Thanks.

Bumping. Any feedback would be helpful.

Zitat von geaves

docker compose up -d is not custom code he's simply deploying the .yaml file he created from the file he created using nano from the command line

Thanks for the info.

Anyways I am still locked out of my OMV5 instance. I need to fix that first before I can fix my NextCloud install problem. Help would be appreciated.

Zitat von geaves

Another option is to run omv-firstaid from the cli and select option 2

I used omv-firstaid and did option 2.

So I did this:

I set HTTP to Port 81

I set HTTPS to Port 443

I am back in and both https://192.168.1.103:81/ and https://192.168.1.103:443/ successfully connect - However it removes the https:// when I connect.

I am using Google Chrome, but I think it is again the server not letting me use TLS/SSL, which is also why I can't fully install and use NextCloud-LetsEncrypt. This is the fundamental issue here.

Any thoughts why it is doing this?