Cloudron Forum

Via a custom script - when I change a version, I have to do this in several places in the app, so I wrote a script where I specify the version number and it does this automatically.

Both. I want to understand if both are correct programmatically, but I can't test them against having an existing docker image, because I find that counter-intuitive - why would I build the docker image before knowing if everything is correct?

@james might be a useful pre-install checklist for setting up a speedy mirror

@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. @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. 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)) 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.

Hi @james Thank you for your feedback. I searched a bit and i found this bug report here in GitHub, it's exactly my problem. Seems to be a bug. When i pres F12 in Firefox, i can see it. First, thought about if i have a wrong configuration, but i guess that Cloudron supports the optimal configuration for Nextcloud, so there's no need to to anything, just wait for the bugfix. https://github.com/nextcloud/server/issues/59468 Has anyone else the same issue? Thanks, Eixen

@ekevu123 Cool app, toying with it right now. One observation: when trying to connect to my nextcloud calendar, it connects and recognizes the different calendars but when I press Add integration, it returns Base url Must be a valid HTTP or HTTPS URL (e.g., https://example.com) nonetheless.

The new package allows to override that variable now in the env.sh file.