Notify_push with docker compose...cannot figure it out at all

wwe · August 26, 2026, 9:06pm

DragonQ:

🗴 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

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)

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 and educate yourself.. e.g. read and understand