NEXTCLOUD_TRUSTED_DOMAINS in docker-compose.yml

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1

Hello together,

I try to get nextcloud running with docker in my local network environment.

I am currently struggeling with the trusted domain. Whatever I try doesn’t seem to work, maybe you can check my setup and tell me if I am doing something wrong.

I want to setup trusted domains in my docker-compose. I added all relevant domains to “NEXTCLOUD_TRUSTED_DOMAINS=” in my docker file, but whatevery I do, nextcloud tells me that I am accesing from a untrusted domain. I currently added every domain/IP I ahve in my network, that contains

  • domain of my router
  • localhost
  • domain of my raspberry
  • host of the docker container

Is there a wildcare or something I can add to the docker-compose file to see if the setting if even recognized by the container?

Is there any logging so I can see which domain is denied?

As I am working in a local network/VPN environment I don’t care aobut trusted domains.

Very unfortunate that setup doesn’t work out of the box… really makes it harded to get into nextcloud.

Best regards

2

Hi @Eleszet welcome to the community of Nextcloud :handshake:

You started a topic in support category. Unfortunately you ignored the template and a lot of information to help you is missing. Please edit your original post and add all required details like Nextcloud version, webserver type and version, os version, related log file content. Use the support template.

Without additional information the community members cannot help you.

Regards,
wwe

2 Likes
3

The only domain that should be in here is the one in the URL itself you wish to use to access Nextcloud.

e.g. mycloud.domain.tld

Very unfortunate that setup doesn’t work out of the box… really makes it harded to get into nextcloud.

Nextcloud has no idea what domain you wish to use. Only you do.

1 Like
4

I think perhaps you have misunderstood what the TRUSTED_DOMAINS parameter is for. This is supposed to contain the domain name of your Nextcloud server that clients will be putting in their web browsers. It should not contain the addresses of other systems.

https://docs.nextcloud.com/server/stable/admin_manual/installation/installation_wizard.html#trusted-domains

2 Likes
5

Hello guys,

thank you all for your answers and sorry for the lack of inmformation I provided. I was in a rush and didn’t prepare the post as careful as I should’ve done.

The solution to my problem was to remove the volume of the nextcloud container. A simple reboot, as I was used to do after changing compose settings, wasn’t sufficient.

It looks like the NEXTCLOUD_TRUSTED_DOMAINS settings in the compose file isn’t checked/updated on restart but only on the initial creation of the volume. Maybe this is mentioned in the documentation somewhere and I missed that.

After re-creating the volume I was able to connect to my nextcloud-docker. I had to set up a proper proxy to avoid the “state missing” problem, but I am currently able to log in and use nextcloud with a single docker-compose file containing nextcloud/postgres/nginx config :+1:

Best regards