I already have a dedicated Nginx Proxy-Manager-running for all my installations on a docker.
I installed Nextcloud using docker compose on an Openmediavault hosted docker.
I set up a “https” proxy on the dedicated Nginx Proxy-Manager forwarded to my Nextcloud install.
When I tried to access it with the setup proxy/domain I set up cloud.mydomain.com, it gives me the following errors:
“Access through untrusted domain
Please contact your administrator. If you are an administrator, edit the “trusted_domains” setting in config/config.php like the example in config.sample.php.”
Thanks for your response.
I did search the forum before asking the question as the answers provided did not address a situation when one already has own Nginx Proxy-Manager on a dedicated machine which provides an https proxy.
It’s a security feature to help prevent spoofing. The SNI must match a name that the server is expecting to see.
Part of the reason so many people have issues with trusted domains right after setup is because some of the guides out there put the cart before the horse and have people run through the initial setup wizard by the IP address. This records the IP address as the sole trusted domain. Then they set up DNS later and suddenly it doesn’t work.
@KarlF12, I can access it directly without ngnix from all browsers, but as soon as I enable ngnix, the restriction kicks in and only Safari can access it.
Not even the Nextcloud app on phone could access it with the domain name, but can access it with the local IP
You have already helped me a lot by taking the time to respond. Thanks a lot for that.
I guess I’ll install another instance of Nginx Proxy Manager and momentary forward port 443 & 80 to the new installation to see what it gives.
I had same problem but different scenario. I have a reverse proxy server accepts url to download files from nextcloud. I got Access through untrusted domain error.
I solved problem by removing X-Forwarded-Host and X-Forwarded-For tags in nginx.conf file like below;