• nginx-config whenever Cloudron box is updated, in an SSH session
• running the script to start notify_push whenever NC app is restarted, using a terminal from Cloudron UI to access the docker container

after running the start script, and using your ps-check command, I see a corresponding process. Additionally, running <occ notify_push:metrics> in a Cloudron terminal shows it works, all indicated stats are up-to-date and change over time.

@andreasb said:

it looks like notify_push is up and running

I honestly don’t understand how you managed to get this working. I spent about 5 hours today trying to set it up and still didn’t get the result I expected.

1. @reboot cron job simply doesn’t work. It’s mentioned in the docs but I’ve never seen it run in the logs. @service does run but only once. Аfter subsequent Nextcloud restarts the job never triggers again.
2. My version of the script works fine if I run it manually from the terminal like this /app/data/notify_push.sh. The service starts and all checks pass.

root@71780ea5-011c-4c09-886e-5f7e17e0b670:/app/code# /app/data/notify_push.sh ; sleep 1 ; ps aux | grep notify_push ; ss -tlnp | grep 7867
✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
✓ push server is a trusted proxy
✓ push server is running the same version as the app
  configuration saved
=> notify_push started on port 7867
root         265  0.3  0.0  25676  8796 ?        Ssl  15:57   0:00 /app/code/apps/notify_push/bin/x86_64/notify_push --allow-self-signed --nextcloud-url http://172.18.20.152 --port 7867 /app/code/config/config.php
root         286  0.0  0.0   4104  2100 pts/1    S+   15:57   0:00 grep --color=auto notify_push
LISTEN 0      128          0.0.0.0:7867       0.0.0.0:*    users:(("notify_push",pid=265,fd=10))

3. If I set up a cron job to run every 5 minutes.
   */5 * * * * echo "=> Enabling notify_push" && /app/data/notify_push.sh
   I can see in the logs that everything looks fine:

Apr 16 18:30:41 ✓ redis is configured
Apr 16 18:30:41 ✓ push server is receiving redis messages
Apr 16 18:30:41 ✓ push server can load mount info from database
Apr 16 18:30:41 ✓ push server can connect to the Nextcloud server
Apr 16 18:30:41 ✓ push server is a trusted proxy
Apr 16 18:30:41 ✓ push server is running the same version as the app
Apr 16 18:30:41 configuration saved
Apr 16 18:30:41 => notify_push started on port 7867

But in reality the process doesn’t survive after the script finishes. If I check manually with
ps aux | grep notify_push ; ss -tlnp | grep 7867 there’s nothing in the terminal.

Claude suggested this might be a cgroup-related issue in containers. The process started from cron gets attached to its cgroup and when the cron job exits, the process is killed along with it. I’m not sure how accurate that is.

Maybe most people who claimed to have notify_push working probably didn’t verify it properly, since the warning disappears from the Nextcloud admin panel. It looks like it’s working, even when it actually isn’t.

1. configure nginx https://forum.cloudron.io/post/48343
2. run notify_push via script https://forum.cloudron.io/post/48298

does the setup work when running sudo -u www-data php -f /app/code/occ notify_push:setup

I don’t think this is possible within Cloudron. For push to work, you need to create a daemon at /etc/systemd/system/notify_push.service and make some changes to Apache or Nginx.
The occ notify_push:setup command assumes that all of this is done on the same server where Nextcloud itself is installed.
However, based on the information from https://github.com/nextcloud/notify_push, it seems that it might be possible to set it up on a separate server — though exactly how to do that is another question.

You can always create a clone from your latest backup and tinker with the clone.
With that approach you risk nothing and can report findings.