# Notify\_push with docker compose...cannot figure it out at all

**URL:** <https://help.nextcloud.com/t/notify-push-with-docker-compose-cannot-figure-it-out-at-all/248604>\
**Category:** ℹ️ Support\
**Tags:** nc34, docker, notify\_push, docker-compose\
**Created:** [August 26, 2026, 3:37pm UTC](https://help.nextcloud.com/t/notify-push-with-docker-compose-cannot-figure-it-out-at-all/248604 "2026-08-26T15:37:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [August 26, 2026, 9:06pm UTC](https://help.nextcloud.com/t/notify-push-with-docker-compose-cannot-figure-it-out-at-all/248604/5 "2026-08-26T21:06:51Z")

</div>

> [@DragonQ](#):
>
> ```auto
> 🗴 push server is not a trusted proxy by Nextcloud or another proxy in the chain.
> Nextcloud resolved the following client address for the test request: "172.20.0.7" instead of the expected "1.2.3.4" test value.
> The following trusted proxies are currently configured: "192.168.1.89", "172.20.0.1"
> The following x-forwarded-for header was received by Nextcloud: "1.2.3.4"
> from the following remote: 172.20.0.7
> 
> ```

notify\_push requests must arrive to the cloud from a #trusted_proxies so you either force the connection through your external domain and reverse proxy or your allow the internal IP.. your IP looks like a Docker internal IP if you have direct connection between the two containers..

if you completely follow the guide you will find

> [@How to docker-compose with notify\_push (2024)](https://help.nextcloud.com/t/how-to-docker-compose-with-notify-push-2024/186721/1):
>
> ```auto
> # all private IPs
> TRUSTED_PROXIES=172.16.0.0/12 192.168.0.0/16 10.0.0.0/8 fc00::/7 fe80::/10 2001:db8::/32
> 
> ```

which likely solves the problem.. if not and the traffic flows through another #reverseproxy this one must trust http headers from notify\_push (similar config as for Nextcloud)

> [@DragonQ](#):
>
> but I’m assuming it’s bad practice to use a local IP here and something isn’t right with my reverse proxy setup?

I don’t think something is wrong with your reverse proxy.. likely it works as expected and doesn’t trust incoming http headers from notify\_push.. but it must. it depends on your setup and intention if it’s right or wrong..

please [use search](https://help.nextcloud.com/search) and educate yourself.. e.g. read and understand

- [GitHub - nextcloud/notify\_push: Update notifications for nextcloud clients · GitHub](https://github.com/nextcloud/notify_push)
- [Setting up Files (High Performance Backend)](https://help.nextcloud.com/t/setting-up-files-high-performance-backend/108651)

---

_[View the full topic](https://help.nextcloud.com/t/notify-push-with-docker-compose-cannot-figure-it-out-at-all/248604)._