Notify Push Container Won't Start - Possible DNS Issue, maybe ipv6?

â„č Support 📩 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

The Basics

  • Nextcloud Server version (e.g., 29.x.x):

    • 32

  • Operating system and version (e.g., Ubuntu 24.04):

    • Truenas 25.04.2.4

  • Reverse proxy and version _(e.g. nginx 1.27.2)

    • Nginx Proxy Manager v2.12.6

  • Is this the first time you’ve seen this error? (Yes / No):

    • yes

  • When did this problem seem to first start?

    • upon first deployment of AIO containers

  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)

    • AIO on custom app (yaml) in Truenas

  • Are you using CloudfIare, mod_security, or similar? (Yes / No)

    • no

Summary of the issue you are facing:

I have a brand new fresh install on Nextcloud AIO v11.9.0 / Nextcloud Hub 25 Autumn and everything gets deployed without any issues except the Notify Push container. I’ve done a little research and this seems to happen from to time, but I was curious of a ‘well known’ solution for this and / or perhaps this is related to the recent release of Hub 25? Seems to be a DNS issues, but why would all the other containers not have an issue but this one does. Logs shown here:

2025-09-30T11:38:36.361505008Z nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9001: Name does not resolve

then a bunch of this

2025-09-30T11:50:52.310282662Z Connection to nextcloud-aio-nextcloud (172.16.2.10) 9001 port \[tcp/\*\] succeeded!
2025-09-30T11:50:52.311989997Z The notify_push binary was not found.
2025-09-30T11:50:52.312031651Z Most likely is DNS resolution not working correctly.
2025-09-30T11:50:52.312039874Z You can try to fix this by configuring a DNS server globally in dockers daemon.json.
2025-09-30T11:50:52.312046316Z See [https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html](https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html)
2025-09-30T11:50:52.312054111Z Afterwards a restart of docker should automatically resolve this.
2025-09-30T11:50:52.312070116Z Additionally, make sure to disable VPN software that might be running on your server
2025-09-30T11:50:52.312077189Z Also check your firewall if it blocks connections to github
2025-09-30T11:50:52.312090741Z If it should still not work afterwards, feel free to create a new thread at [https://github.com/nextcloud/all-in-one/discussions/new?category=questions](https://github.com/nextcloud/all-in-one/discussions/new?category=questions) and post the Nextcloud container logs there.
2

confirmed this has to be ipV6 related; i disabled ipv6 on WAN and LAN and the notify-push started right away.