# After upgrade to 29 getting trusted\_proxies error

**URL:** <https://help.nextcloud.com/t/after-upgrade-to-29-getting-trusted-proxies-error/189016>\
**Category:** ℹ️ Support\
**Tags:** reverseproxy, github\_issue\_required, setup\_warning\
**Created:** [April 25, 2024, 6:20am UTC](https://help.nextcloud.com/t/after-upgrade-to-29-getting-trusted-proxies-error/189016 "2024-04-25T06:20:09Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![flotillaropes](https://help.nextcloud.com/letter_avatar/flotillaropes/32/6_22734026db12803ebb3e059622ac3534.png) [@flotillaropes](https://help.nextcloud.com/u/flotillaropes)\
**Post date:** [April 25, 2024, 9:12am UTC](https://help.nextcloud.com/t/after-upgrade-to-29-getting-trusted-proxies-error/189016/7 "2024-04-25T09:12:24Z")

</div>

> [@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 not considered.

I added a reply [here](https://github.com/nextcloud/server/pull/44495) which will hopefully receive a timely response.

---

_[View the full topic](https://help.nextcloud.com/t/after-upgrade-to-29-getting-trusted-proxies-error/189016)._
