Update to 29. Check overview. New error: There are some errors regarding your setup. Your “trusted_proxies” setting is not correctly set, it should be an array of IP addresses - optionally with range in CIDR notation. I run linuxserver nextcloud container and reverse proxy through linuxserver swa…

Graciously addressed quickly by the dev team. Thank you! I suggest reading the thread for the explanation, but in summary: However you could do this: 'trusted_proxies' => array ( 0 => gethostbyname('swag'), ),

[image] flotillaropes: fix(settings): Also verify that `trusted_proxies` only contains IP addresses (with range) · 3203db8160 - mirrors/nextcloud-server - Sadium Git This links to a third party site. Here’s the original Pull Request in the Nextcloud server repo. So yes they seem to have adde…

It’s not issuing a warning. It’s issuing an error with a big red X. The big question is can this error be ignored? It appears it can as nextcloud is working and throwing no errors and the log is clean. My understanding is if trusted proxy is incorrect, nextcloud will throw an error and be unreachabl…

[image] flotillaropes: The big question is can this error be ignored? It appears it can as nextcloud is working and throwing no errors. I don’t know. But opening an issue might be a good way to find out :wink: [image] flotillaropes: It’s worth mentioning the last time I documented an imp…

Understood, but probably won’t repeat the effort. However, if someone can verify my understanding that if the trusted proxy is set incorrectly, nextcloud will display a trusted proxy error and not work. Is this correct?

[image] flotillaropes: nextcloud will display a trusted proxy error and not work. Is this correct? Well, I’d guess so. But, it’s also quite possible that the check does not actually perform a function check, but only looks at the values in config.php and then complains if it finds anything o…

[image] bb77: And yes, it is quite possible that the check does not actually perform a function check, but only looks at the values in config.php and then complains if it finds anything other than IP addresses. In this context, it is of course also possible that your Docker scenario was simply n…

Same problem… nextcloud is running in a container my config looks like: ‘trusted_proxies’ => [‘192.168.10.70’, ‘172.17.0.1’, ‘127.0.0.1’], In the access-logs I can see connections from my reverse proxy 192.168.10.70 … not good, because my fail2ban cant allocate failed logins from real clients an…

I had a similar Issue and tried some config with IP of the server and w/o. Now it’s “127.0.0.1” only, and the error disappeared. Not sure if this is a solution we were looking for, but I will keep an eye on it with upcoming patches.

So after messing around with this for a few minutes, I used the IP with no ports instead of the website name and it worked. Not sure if that’s what we need but I don’t see the error anymore. ‘trusted_proxies’ => array ( 0 => ‘255.25.255.255’, ),

After upgrade to 29 getting trusted_proxies error

ℹ️ Support

flotillaropes April 25, 2024, 9:12am 7

I added a reply here which will hopefully receive a timely response.