-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get 404 on notify_push:setup #89
Comments
It looks like notify_push doesn't accept http/2 requests. |
I found a solution. The provided reverse proxy from uberspace doesn’t set the necessary header. |
@mariusbertram Could you share your solution, I am currently facing the same problem with my setup. |
I set up an extra nginx as a second reverse proxy. And point the uberspace backend to the nginx. |
Which header was missing in your case? |
Here is the Issue for the Uberspace lab Uberspace/lab#1004 . |
I'm suffering from the same problem, and I could rule out that it is related to http/2. Trace log of notify_push shows the following when doing
Hence: ./scripts/occ.sh notify_push:setup https://breitbandig.local:8443/nextcloud/push
+ podman exec -it --user www-data nc_app_1 php /var/www/html/occ notify_push:setup https://breitbandig.local:8443/nextcloud/push
✓ redis is configured
🗴 can't connect to push server: Client error: `GET https://breitbandig.local:8443/nextcloud/push/test/cookie` resulted in a `404 Not Found` response |
I couldn't get notify_push getting to work with the fairly complex proxy setting at my hosting provider.
|
With the new version it's now working for me. |
I have the exact same problem as the people above did. Using the binary that comes with app version 0.4.0 on armv7l. Running it in docker, in a separate container, but the config is mounted, and apparently it can connect to both NC, the DB and Redis. Same output in the trace log. I double-checked that I have the same header settings in nginx as explained in the readme. What might still be wrong? I couldn't find any useful pointers among the above comments. |
I try to get notify_push running on uberspaec. It's a shared hoster where you can set own backend services.
On my virtual network I can access the notify_push /test/cookie path. But not behind the proxy.
On the setup I receive an 404 error.
The trace log from notify_push:
The text was updated successfully, but these errors were encountered: