Comments (11)
ivulit
commented on July 17, 2024
1
I've changed PUSH_RELAY_URI to https://api.bitwarden.eu and push service works again for me
from vaultwarden.
CTXP
commented on July 17, 2024
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.
from vaultwarden.
stefan0xC
commented on July 17, 2024
Hm... not sure what's wrong. Here's a LOG_LEVEL=debug log of the registration attempt:
[2024-06-03 21:56:33.834][request][INFO] PUT /api/devices/identifier/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/token
[2024-06-03 21:56:33.837][vaultwarden::api::push][DEBUG] Registering Device xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
[2024-06-03 21:56:33.846][reqwest::connect][DEBUG] starting new connection: https://identity.bitwarden.eu/
[2024-06-03 21:56:33.847][hyper_util::client::legacy::connect::dns][DEBUG] resolving host="identity.bitwarden.eu"
[2024-06-03 21:56:33.877][hyper_util::client::legacy::connect::http][DEBUG] connecting to 199.232.17.91:443
[2024-06-03 21:56:33.892][hyper_util::client::legacy::connect::http][DEBUG] connected to 199.232.17.91:443
[2024-06-03 21:56:33.911][h2::client][DEBUG] binding client connection
[2024-06-03 21:56:33.911][h2::client][DEBUG] client connection bound
[2024-06-03 21:56:33.911][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:33.911][h2::proto::connection][DEBUG] Connection; peer=Client
[2024-06-03 21:56:33.911][hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", identity.bitwarden.eu)
[2024-06-03 21:56:33.912][h2::codec::framed_write][DEBUG] send frame=WindowUpdate { stream_id: StreamId(0), size_increment: 5177345 }
[2024-06-03 21:56:33.917][h2::codec::framed_write][DEBUG] send frame=Headers { stream_id: StreamId(1), flags: (0x4: END_HEADERS) }
[2024-06-03 21:56:33.918][h2::codec::framed_write][DEBUG] send frame=Data { stream_id: StreamId(1), flags: (0x1: END_STREAM) }
[2024-06-03 21:56:33.923][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x0), max_concurrent_streams: 100 }
[2024-06-03 21:56:33.923][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:33.923][h2::codec::framed_read][DEBUG] received frame=WindowUpdate { stream_id: StreamId(0), size_increment: 16711681 }
[2024-06-03 21:56:33.923][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:33.924][h2::proto::settings][DEBUG] received settings ACK; applying Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:34.032][h2::codec::framed_read][DEBUG] received frame=Headers { stream_id: StreamId(1), flags: (0x4: END_HEADERS) }
[2024-06-03 21:56:34.032][h2::codec::framed_read][DEBUG] received frame=Data { stream_id: StreamId(1) }
[2024-06-03 21:56:34.032][h2::codec::framed_read][DEBUG] received frame=Data { stream_id: StreamId(1), flags: (0x1: END_STREAM) }
[2024-06-03 21:56:34.033][vaultwarden::api::push][DEBUG] Token still valid for 43199
[2024-06-03 21:56:34.033][reqwest::connect][DEBUG] starting new connection: https://push.bitwarden.eu/
[2024-06-03 21:56:34.033][hyper_util::client::legacy::connect::dns][DEBUG] resolving host="push.bitwarden.eu"
[2024-06-03 21:56:34.058][hyper_util::client::legacy::connect::http][DEBUG] connecting to [2606:4700:3035::6815:195f]:443
[2024-06-03 21:56:34.072][hyper_util::client::legacy::connect::http][DEBUG] connected to [2606:4700:3035::6815:195f]:443
[2024-06-03 21:56:34.095][h2::client][DEBUG] binding client connection
[2024-06-03 21:56:34.096][h2::client][DEBUG] client connection bound
[2024-06-03 21:56:34.096][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:34.096][h2::proto::connection][DEBUG] Connection; peer=Client
[2024-06-03 21:56:34.096][hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", push.bitwarden.eu)
[2024-06-03 21:56:34.096][h2::codec::framed_write][DEBUG] send frame=WindowUpdate { stream_id: StreamId(0), size_increment: 5177345 }
[2024-06-03 21:56:34.096][h2::codec::framed_write][DEBUG] send frame=Headers { stream_id: StreamId(1), flags: (0x4: END_HEADERS) }
[2024-06-03 21:56:34.097][h2::codec::framed_write][DEBUG] send frame=Data { stream_id: StreamId(1), flags: (0x1: END_STREAM) }
[2024-06-03 21:56:34.107][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x0), max_concurrent_streams: 100, initial_window_size: 65536, max_frame_size: 16777215 }
[2024-06-03 21:56:34.107][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:34.108][h2::codec::framed_read][DEBUG] received frame=WindowUpdate { stream_id: StreamId(0), size_increment: 2147418112 }
[2024-06-03 21:56:34.108][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:34.108][h2::proto::settings][DEBUG] received settings ACK; applying Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:34.140][h2::codec::framed_read][DEBUG] received frame=Headers { stream_id: StreamId(1), flags: (0x5: END_HEADERS | END_STREAM) }
[2024-06-03 21:56:34.141][reqwest::async_impl::client][DEBUG] redirecting 'https://push.bitwarden.eu/push/register' to 'https://api.bitwarden.eu/push/register'
[2024-06-03 21:56:34.141][reqwest::connect][DEBUG] starting new connection: https://api.bitwarden.eu/
[2024-06-03 21:56:34.142][hyper_util::client::legacy::connect::dns][DEBUG] resolving host="api.bitwarden.eu"
[2024-06-03 21:56:34.159][hyper_util::client::legacy::connect::http][DEBUG] connecting to 199.232.17.91:443
[2024-06-03 21:56:34.172][hyper_util::client::legacy::connect::http][DEBUG] connected to 199.232.17.91:443
[2024-06-03 21:56:34.190][h2::client][DEBUG] binding client connection
[2024-06-03 21:56:34.191][h2::client][DEBUG] client connection bound
[2024-06-03 21:56:34.191][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:34.191][h2::proto::connection][DEBUG] Connection; peer=Client
[2024-06-03 21:56:34.191][hyper_util::client::legacy::pool][DEBUG] pooling idle connection for ("https", api.bitwarden.eu)
[2024-06-03 21:56:34.191][h2::codec::framed_write][DEBUG] send frame=WindowUpdate { stream_id: StreamId(0), size_increment: 5177345 }
[2024-06-03 21:56:34.192][h2::codec::framed_write][DEBUG] send frame=Headers { stream_id: StreamId(1), flags: (0x5: END_HEADERS | END_STREAM) }
[2024-06-03 21:56:34.202][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x0), max_concurrent_streams: 100 }
[2024-06-03 21:56:34.202][h2::codec::framed_write][DEBUG] send frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:34.202][h2::codec::framed_read][DEBUG] received frame=WindowUpdate { stream_id: StreamId(0), size_increment: 16711681 }
[2024-06-03 21:56:34.202][h2::codec::framed_read][DEBUG] received frame=Settings { flags: (0x1: ACK) }
[2024-06-03 21:56:34.202][h2::proto::settings][DEBUG] received settings ACK; applying Settings { flags: (0x0), enable_push: 0, initial_window_size: 2097152, max_frame_size: 16384, max_header_list_size: 16384 }
[2024-06-03 21:56:34.315][h2::codec::framed_read][DEBUG] received frame=Headers { stream_id: StreamId(1), flags: (0x5: END_HEADERS | END_STREAM) }
[2024-06-03 21:56:34.316][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 21:56:34.317][response][INFO] (put_device_token) PUT /api/devices/identifier/<uuid>/token => 400 Bad Request
If I try to register with PUSH_RELAY_URI=https://api.bitwarden.eu it seems to work. So it might be an issue with the redirection or the reqwest crate?
from vaultwarden.
Opicka879
commented on July 17, 2024
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.
[2024-06-03 23:19:47.637][error][ERROR] 2FA token not provided
[2024-06-03 23:20:06.938][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:21:43.193][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:22:04.334][vaultwarden::api::icons][WARN] Unable to download icon: Empty response or unable find a valid icon. www.bitbeli.cz
[2024-06-03 23:28:27.016][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:28:27.017][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:28:27.695][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:28:27.724][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:28:40.444][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:28:40.479][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:28:57.530][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:28:57.549][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:29:08.124][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:29:08.133][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:29:30.136][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:30:06.831][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:30:34.856][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:30:50.318][vaultwarden::api::push][ERROR] An error occurred while proceeding registration of a device: HTTP status client error (405 Method Not Allowed) for url (https://api.bitwarden.eu/push/register)
[2024-06-03 23:35:29.371][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:35:29.398][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
[2024-06-03 23:35:44.880][vaultwarden::api::web][ERROR] Static file not found: jquery-3.7.0.slim.js
[2024-06-03 23:35:44.897][vaultwarden::api::web][ERROR] Static file not found: jdenticon.js
from vaultwarden.
Kaskadee
commented on July 17, 2024
If I try to register with
PUSH_RELAY_URI=https://api.bitwarden.euit seems to work. So it might be an issue with the redirection or the reqwest crate?
Changing to https://api.bitwarden.eu no longer results in an error message, but it seems that push notifications are still not working? When I tried the US data region, I immediately received the update notification when I created or deleted a folder, but no reaction when using the EU data region.
Could be a problem with Bitwarden though.
from vaultwarden.
Kaskadee
commented on July 17, 2024
Could be a problem with Bitwarden though.
I've just tested creating a new item at https://bitwarden.eu and push notifications are working correctly there.
from vaultwarden.
Opicka879
commented on July 17, 2024
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.
from vaultwarden.
CTXP
commented on July 17, 2024
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!
from vaultwarden.
FlakyPi
commented on July 17, 2024
I've changed PUSH_RELAY_URI to https://api.bitwarden.eu and push service works again for me
Same here, everything works again.
from vaultwarden.
Kaskadee
commented on July 17, 2024
I have forgotten to set PUSH_ENABLED back to true, that's why it didn't work :)
It works now with PUSH_RELAY_URI set to https://api.bitwarden.eu/
from vaultwarden.
Kitchigo
commented on July 17, 2024
Yeah, thank you It's working again with "https://api.bitwarden.eu/"
from vaultwarden.
Related Issues (20)
- Error running migrations: QueryError(DieselMigrationName HOT 1
- WEB_VAULT_ENABLED can not be changed from ENV_FILE, but it is implied that it can be
- Warm users about access key leakage in access logs HOT 4
- v2024.5.0 doesn't allow one to enroll in account recovery HOT 3
- Missing Icons HOT 4
- Cannot re-send invitation to organisation when invitations_allowed==false HOT 2
- Import errors with KeePass 1.0 CSV
- Does not compile with rust 1.79 HOT 2
- DB schema: Foreign keys invalid
- Biometrics error while using Passkeys HOT 25
- Cannot Login Using Bitwarden Mobile Native HOT 11
- Convoluted cloudflare tunnel instructions (No insult intended just curious). HOT 2
- Account name not appearing when using a passkey on Android HOT 3
- Chrome extension fails CORS due to missing origin HOT 1
- <USERNAME> tag required in regex in fail2ban setup docs
- Creation, edits and delete of entries slow 5+ seconds each HOT 3
- No MasterPassword login after increase KDF HOT 8
- can not login with bitwarden android 2024.6.1-beta (11139) HOT 1
- Extension Update Item Collections returns Error HOT 2
- [Bug] Latest testing, collections do not load (Related to PascalCase changes?) HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vaultwarden.