Orejo

Thank you, appreciate your quick response. I can now access nextcloud locally, thanks! I moved unraid‘s https port to a different port and let letsencrypt run on 443; the letsencrypt http port is still on 81. Can I leave it as is or do I need to change the http port from either unraid or the letsencrypt container?

I'm experiencing a strange issue. When I'm accessing Nextcloud locally, I get redirected to the unRAID dashboard and I get to see the login prompt for the dashboard. When I'm outside my network, the connection works fine. I have other services set up, such as Sonarr and Radarr, both of which work fine externally and internally. I've attached my config files. config.php nextcloud.subdomain.conf

I‘ve been experiencing an odd issue recently: For some reason, I cannot access the sites behind the reverse proxy when I‘m in the same network as my server. When connecting from outside my network (i.e. tethering), I can access Nextcloud, which is one of the programs sitting behind the reverse proxy, just fine. I think that the error occurred after summertime was over. Not sure though, but I‘m assuming it was around that time. I‘d appreciate any hints.

First of all, thanks a lot for creating this docker container. I‘ve run into a couple of issues, I simply couldn‘t solve myself. What I‘ve done so far: 1) I opened ports 80 and 443 on my router and forwarded them to 1880 and 18443 on the server. Both ports seem to be open. 2) I set up a DuckDNS container and verified that it shows my public IP. 3) I registered a domain and created a few CNAMES, i.e. sonarr.mydomain.com and plex.mydomain.com, both of which point to the DuckDNS domain (see above). I pinged sonarr.mydomain.com to verify that I see my public IP and it worked. 4) I installed the Nginx Proxy Manager docker and it proceeded without any errors. I didn’t have to set up a MariaDB database, which was odd for me, because I thought I‘d have to create a DB on my own. I then changed the admin password and I was able to access the GUI. 5) I created a new host entry for Sonarr and I used HTTP to check if it works. After that, I was able to access sonarr.mydomain.com. To secure it, I then wanted to set up https with a LE cert. I opened the Sonarr container, enabled SSL and headed back to the Nginx Proxy Manager docker, where I switched the host entry to https and change the port according to Sonarr‘s SSL port. Problem: This is where I got stuck. I couldn‘t access the site anymore and had to switch back to HTTP. For now, I’ve closed both ports for security reasons before I sit down and try to solve the issue with your appreciated input. Tl;dr: HTTP access works, HTTPS doesn‘t. Both ports seem to be forwarded correctly, custom domain.