Try, if you haven’t, rebooting the disk station on which the reverse proxy was set up. Also try accessing from a different machine from outside your LAN.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
Or maybe you asking what happens if I type https://nextcloud.myserver.tld. It goes to the Synology page. And https://server.mydomain.tld:8080, Safari can't establish a secure connection to the server server.mydomain.tld. But I can access port 1234 for DSM.is your RP for NC working on 443 if you explicitly direct it to https?
OK, I've deleted the HTTPS RP (as shown above) and recreated it. No problem saving this time but no change in result.That means that RP is the probelm.
I've deleted all the Reverse Proxy and Virtual Host stuff, deleted then reinstalled MariaDB, phpMyAdmin and Nextcloud.Can I break this down more?
So looks like you are not using RP in this case but accessing your services directly? Whats the real error/outcome in this case?Then why can't I access Nextcloud at myserver.mydomain.tld:8080 or phpMyAdmin at myserver.mydomain.tld:8081?
Completely correct. You are using https protocol to access your services using an IP address that is not covered by your SSL cert/domain name. Most browsers nowadays will report this problem and not allow a connectionSafari can’t open the page “https://192.168.1.2:8080” because Safari can’t establish a secure connection to the server “192.168.1.2”
Safari can’t open the page “https://myserver.mydomain.tld:8080” because Safari can’t establish a secure connection to the server “myserver.mydomain.tld”Whats the real error/outcome in this case?
I do have a certificate for myserver.mydomain.tld so even if I get the block for the IP address, why also for the FQDN?You are using https protocol to access your services using an IP address that is not covered by your SSL cert/domain name. Most browsers nowadays will report this problem and not allow a connection
Not at the moment. I've disabled all the proxies and forwards to try and establish where my problem originates. So although I have no HTTP to HTTPS forwards set up, I keep getting forwarded to HTTPS when requesting a HTTP page.Have you enable HSTS for the reverse proxy rule? That should direct any HTTP to HTTPS.
It's not set up at the minute but as I recall the certificate was assigned to the subdomain 'nextcloud'.In Control Panel -> Security -> Certificates there's a Configure button that open a list for assigning certificates to services.
See, everyone is one step ahead of me! That wasn't the problem but is now. As I understand (which is lacking) Docker was meant to add the trusted domains to the config.php on creation as I added them to the Environment section. But it didn't so all I have to do is roll up my sleeves and get stuck in with the command line.could it be a problem with trusted domains in nextcloud's configuration file?
Yes, I remember now. And it has instructions at the bottom of the window!nano is easy