Support intro
Sorry to hear you’re facing problems. 
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:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(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:
32.0.3 AIO
- Operating system and version:
Ubuntu 22.04
- Web server and reverse proxy:
nginx 1.28.0 mainline PPA
- Is this the first time you’ve seen this error?:
-
I can't even....
- Installation method
-
AIO
- Are you using CloudfIare, mod_security, or similar?
nope
Summary of the issue you are facing:
Many of my users sit behind the Great Firewall of China, and they use domestic mobile phones which come with crippled Android derivatives lacking most Google frameworks. Hence they are not able to receive notifications from applications we in the rest of the world are used to receive. This e.g. renders Nextcloud Talk useless, but we have certain needs concerning our business processes when it comes to custom notifications about activities as well.
So I want to add a push provider in order to provide our users with notifications both on the desktop and their mobile phones.
My problem is that I do not understand which of all of these push here, push there Nextcloud apps and binaries actually do what and how. For testing purposes I installed NextPush from F-Droid on my phone and then - accompanied by some headaches due to IP range restrictions from Codeberg - I deployed uppush on our server. OK, what does this actually do? The documentation is an unholy mess. Moving on to Client Push, Notify_Push….
I noticed the AIO instance comes with aaio-notify-push container. Okay, so far so good. How to configure that? Where is the documentation? How to add/change configuration? I am using docker compose here. I am facing 502 errors as the notify_push upstream cannot connect to the reverse proxy. (Oh… how much I despise and hate Docker networking)
Digging deeper into the problem revealed that obviously the notify-push container needs an env variable NEXTCLOUD_URL = bla.domain.fasel, but how to pass this on to the container? I can’t add the variable through portainer, I can’t find the freaking env directives in the respective container, and I guess once pulling the upgraded images these variables will be gone too.
2026/01/09 23:59:39 [error] 599869#599869: *24810 connect() failed (111: Connection refused) while connecting to upstream, client: 111.222.333.444, server: bla.domain.fasel, request: “GET /push/ws HTTP/1.1”, upstream: “``http://172.18.0.1:7867/ws”``, host: “bla.domain.fasel”
I added the location block in our Nginx reverse proxy conf according to the documentation, yet I fail to understand where in the darn seven hells and seven seas for the love of God Docker even listens to host ports in this delightful aio-network, and how I can make notify_push and Nginx talk to each other. I tried to expose port 7867, I tried several different proxy_pass directives (127.0.0.1, 172.18.0.1, 172.18.0.3, and so on), yet I still always receive the same error mentioned above.
location ^~ /push/ {
#proxy_pass http://127.0.0.1:7867/;
proxy_pass http://172.18.0.1:7867/; # dafuq?
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
I tried to set up notify_push as instructed in the documentation. Is this even necessary on AIO? It shouldn’t be, no?
occ notify_push:self-test fails with:
✓ redis is configured
🗴 can't connect to push server: Server error: `GET https://bla.domain.fasel/push/test/cookie` resulted in a `502 Bad Gateway` response:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>ngin (truncated...)
Of course occ notify_push:setup fails as well. Sending a payload through CLI works and my desktop application happily sent me a nice notification which also showed up in the Nextcloud webui.
Nextcloud Logs:
Here be dragons. Good luck finding anything related to aio-notify-push errors. Pffff
It is just deeply frustrating to try making this functional. Please bear with me, my knowledge of Docker is limited, as I come from the LXD, LXC, Juju, Ansible, Puppet, Terraform world. We have been using Nextcloud before it even was Nextcloud (ownCloud), but this whole AIO thing on Docker … sometimes it just does not make any sense to me. Can anybody enlighten me on how to wade through this valley of tears in order to get push notifications on the phones of our users?