search

nextcloud / notify_push

Update notifications for nextcloud clients
GNU Affero General Public License v3.0
229 stars 42 forks source link

[1.7] self-test says that everything's fine but binary presumably not reachable / no notifications sent #80

Open Nick-Git2 opened 3 years ago

Nick-Git2 commented 3 years ago

Ubuntu 20.04 LTS, NC21.0.1 / notify_push 1.7

$ sudo -u www-data /var/www/nextcloud/occ notify_push:self-test ✓ 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

$ sudo -u www-data /var/www/nextcloud/occ notify_push:setup This setup wizard is intended for use on single server instances where the nextcloud server, web server/reverse proxy and push daemon all run on the same machine. If your setup is more complex or involves any kind of load balancing you should follow the manual setup instruction on the README instead https://github.com/nextcloud/notify_push Press enter to continue or ESC to cancel...

🗴 'overwrite.cli.url' is set to localhost, the push server will not be reachable from other machine s Push binary seems to be running already ✓ push server seems to be functioning correctly. Run the following commands to enable the proxy modules sudo a2enmod proxy sudo a2enmod proxy_http sudo a2enmod proxy_wstunnel

Then place the following within the block of the apache config for your nextcloud installation which can usually be found within /etc/apache2/sites-enabled/ Note that there might be both an http and https config file

ProxyPass /push/ws ws://127.0.0.1:7867/ws ProxyPass /push/ http://127.0.0.1:7867/ ProxyPassReverse /push/ http://127.0.0.1:7867/

And reload apache using sudo systemctl restart apache2 Press enter to continue or ESC to cancel...

🗴 push binary doesn't seem to be reachable trough the reverse proxy, did you follow the above instr uctions?. See the steps in the README for manual setup instructions: https://github.com/nextcloud/notify_push

$ sudo systemctl status notify_push ● notify_push.service - Push daemon for Nextcloud clients Loaded: loaded (/etc/systemd/system/notify_push.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-04-14 19:23:49 CEST; 29min ago Main PID: 3565 (notify_push) Tasks: 4 (limit: 4618) Memory: 2.0M CGroup: /system.slice/notify_push.service └─3565 /var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php

Apr 14 19:23:49 YYYYYYYvsa systemd[1]: Started Push daemon for Nextcloud clients.

icewind1991 commented 3 years ago

Can you try running the test client as described here: https://github.com/nextcloud/notify_push#test-client with debug logging enabled (occ notify_push:log debug)

Nick-Git2 commented 3 years ago

$ sudo -u www-data /var/www/nextcloud/occ notify_push:log debug $ test_client https://XXXXX YYYYY ZZZZZ Found push server at wss://XXXXX/push/ws Authenticated (FYI: test_client did not return to shell after "Authenticated")

Interestingly, the notification seems to work at the moment despite no changes/reboot or whatsoever since yesterday when it didn't work! Anyway, I'm still getting this error message when executing occ notify_push:setup: 🗴 push binary doesn't seem to be reachable trough the reverse proxy, did you follow the above instr uctions?.

tanandry commented 3 years ago

I have the same problem with the setup but with Nginx. Before 1.7 my reverse proxy settings worked fine, but this recent update suddenly made it unable to connect.

Mer0me commented 1 year ago

I have the same problem with NC25.03 push server 0.5.0. Any clue ?