-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Mobile Push Notification registration returns HTTP 405 for EU data region #4609
Comments
I have the same Issue, I just set this up and was wondering why it isn't working and found the same error message in my logs. |
Hm... not sure what's wrong. Here's a
If I try to register with |
Same issue here. Notification stoped working some time ago but i dont know when exactly. I thought it is problem of android app but today i did try to update from latest release to testing, regenerate push relay uri and push identity uri, clear app cache and it is still not working and now i have same line in the log. [2024-06-03 23:16:50.384][rocket::server][WARN] Received SIGTERM. Requesting shutdown. |
Changing to
|
I've just tested creating a new item at |
After changing the push relay uri to https://api.bitwarden.eu/ instant changes works for me too and there is no error in log. But i still have no pop-up window with login requests if i want to log in via device. It can be android app bug i quess. |
To fix my problem, I had to explicitly enable web socket support in NPM, this made my realize that using the network tab in the browser helps a ton while debugging errors in Vaultwarden it has much clearer error details! |
I've changed PUSH_RELAY_URI to https://api.bitwarden.eu and push service works again for me |
Same here, everything works again. |
I have forgotten to set |
Yeah, thank you It's working again with "https://api.bitwarden.eu/" |
Updating the Updating the |
Subject of the issue
Following the instructions at https://github.com/dani-garcia/vaultwarden/wiki/Enabling-Mobile-Client-push-notification for using mobile push notifications with the EU data region causes a 405 Method Not Allowed when Vaultwarden attempts to register the device:
Removing
PUSH_RELAY_URI
+PUSH_IDENTITY_URI
and regenerating a new installation ID + key in the US data region works fine:Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Expected behaviour
Mobile Push Notifications with the EU data region work the same as with the US data region
Actual behaviour
Device registration returns
405 Method Not Allowed
Troubleshooting data
See the log entries above.
The text was updated successfully, but these errors were encountered: