[Bug]: After update to 29: Some headers are not set correctly on your instance

[jiriks74]

[Bug]: After update to 29: Some headers are not set correctly on your instance

[jiriks74]

Got rid of it by modifying the compose file. The setup I used as a base had a hostname defined and that's why it resolved to the container and not the proxy.

[0x09AF]

I don't have hostname configured in my compose file, but got this error after upgrading to 29. Is there another fix?

[jiriks74]

What is your setup. Like is the server local, behind proxy, etc. What IP is the container resolving the hostbame to? (Run dig your.domain inside the container)

[warioishere]

I dont use docker, just plain selft installation

[joshtrichards]

Do each of your configured trusted_domains resolve to your proxy/TLS terminator from the perspective of your Nextcloud Server? That is, if you run curl from within your Nextcloud Docker container does it hit your proxy (and therefore see those headers)? That's the most common culprit since most of the tests are running from the server itself rather than you're browser these days.

[jiriks74]

For whatever reason dig running directly from the container resolves to the container IP rather than the public one.

[mikesteele81]

I have the same problem. With Nextcloud 28 I made sure that the self-test would hit the reverse proxy's internal address by including an entry within /etc/hosts to override what DNS would otherwise provide.

[VPaulV]

I have the same issue. Could you please provide instructions on how to fix it?

[jiriks74]

I have the same issue. Could you please provide instructions on how to fix it?

Like I said, remove/change the hostname: nextcloud.somedomain.eufrom your compose file

[0x09AF]

@jiriks74 I am not too sure if I have the exact same error but the symptoms are similar, appeared after upgrading to v29. Here's the error: Could not check that your web server serves security headers correctly, unable to query `` For more details see the documentation ↗
dig inside the container resolves the same as from the outside - to Cloudflare IPs

[wvxx]

I'm having the same issue since upgrading to 29, dig ran from within the container resolves to my public IP address, I've no hostname set on my container as well, trusted proxies are set properly.

Any ideas? ;)
Thanks.

[jiriks74]

@0x09AF

unable to query ``

This seems like Nextcloud doesn't have it's hostname set properly?

I've no hostname set on my container as well, trusted proxies are set properly.

If it's the same error I suspect that Nextcloud doesn't know it's url and you cannot query an empty string

---

What are your proxy settings?

[wvxx]

If it's the same error I suspect that Nextcloud doesn't know it's url and you cannot query an empty string

What are your proxy settings?

I might have expressed myself a bit unclearly. I mean that I get the warnings in my nextcloud admin settings despite curl telling me that all headers are enabled.

I have trusted_proxies set to IP of my traefik container as well as public IP, like I said above dig ran from the nextcloud container shows my public IP address.

[0x09AF]

@0x09AF

unable to query ``

This seems like Nextcloud doesn't have it's hostname set properly?
My docker-compose hasn't changed in a few years I have been running Nextcloud. Could you point me to the right env variable or a line in config.php?
Thanks

[warioishere]

I am also having this issue, baremetal nextcloud installation. I dont havy any ReverseProxy infront of my NC
they headers are set if i curl my domain.

[tuxArg]

Hi, I've just had this message too. I solved it allowing container IP login in limit_login_to_ip app. I hope it helps.

[xundeenergie]

Same here. Plain installation without container... and i get the same warnings Since upgrade to 29.

[lexxxel]

same, I run nextcloud from a lxc container and checked with curl - everything looks OK from there. (My reverse proxy is also traefik on another lxc container somewhere in the network)