Hi,
I am struggling to get /notifications/hub to work if I browse to the URL I get a 404 error, I am using docker as a host and am currently on version 1.29.1
I am behind HA proxy, however even bypassing that on my local network and going direct to the server I get the same 404 error.
Does anyone have any ideas?
Thanks
That endpoint is used for upgrading websocket requests . I.e. it does not serve anything if you try manual GET requests.
Ah ok, it used to return {} when using websockets so I guess that is different now. What is the best way to see if my iPhone has a push token? It’s not currently working and I have removed the app deauthd all sessions, reinstalled the app and logged back in but still nothing. Is there anything I can check?
I don’t think that endpoint is used for mobile push notifications. Have you enabled Mobile Client push notifications? If so, you can use the second method of the linked article in my previous post to see if it works (i.e. change something in the web-vault and see if it is synced automatically in the mobile client).
To make sure if mobile push notifications work you can also check the logs with LOG_LEVEL=debug and (e.g., after changing a folder name in your personal vault) you should see calls to push.bitwarden.com like this:
Aug 19 09:36:35 vanity vaultwarden-app[916632]: [2023-08-19 07:36:35.884][response][INFO] (put_folder) PUT /api/folders/<uuid> => 200 OK
Aug 19 09:36:35 vanity vaultwarden-app[916632]: [2023-08-19 07:36:35.885][vaultwarden::api::push][DEBUG] Auth Push token still valid, no need for a new one
Aug 19 09:36:35 vanity vaultwarden-app[916632]: [2023-08-19 07:36:35.989][reqwest::connect][DEBUG] starting new connection: https://push.bitwarden.com/
Aug 19 09:36:35 vanity vaultwarden-app[916632]: [2023-08-19 07:36:35.990][trust_dns_proto::xfer::dns_handle][DEBUG] querying: push.bitwarden.com A
I did yes, the log shows this.
;; identity.bitwarden.com. IN A
[2023-08-19 16:10:37.005][trust_dns_proto::udp::udp_stream][DEBUG] created socket successfully
[2023-08-19 16:10:37.031][trust_dns_proto::udp::udp_client_stream][DEBUG] received message id: 20329
[2023-08-19 16:10:37.031][trust_dns_resolver::error][DEBUG] Response:; header 20329:RESPONSE:RD,RA:NoError:QUERY:2/0/0
; query
;; identity.bitwarden.com. IN A
; answers 2
identity.bitwarden.com. 191 IN A 104.18.12.33
identity.bitwarden.com. 191 IN A 104.18.13.33
; nameservers 0
; additionals 0
[2023-08-19 16:10:37.031][trust_dns_resolver::error][DEBUG] Response:; header 20329:RESPONSE:RD,RA:NoError:QUERY:2/0/0
; query
;; identity.bitwarden.com. IN A
; answers 2
identity.bitwarden.com. 191 IN A 104.18.12.33
identity.bitwarden.com. 191 IN A 104.18.13.33
; nameservers 0
; additionals 0
[2023-08-19 16:10:37.561][vaultwarden::api::push][DEBUG] Token still valid for 43199
[2023-08-19 16:10:37.561][trust_dns_proto::xfer::dns_exchange][DEBUG] io_stream is done, shutting down
[2023-08-19 16:10:37.568][reqwest::connect][DEBUG] starting new connection: https://push.bitwarden.com/
[2023-08-19 16:10:37.568][trust_dns_proto::xfer::dns_handle][DEBUG] querying: push.bitwarden.com A
[2023-08-19 16:10:37.568][trust_dns_resolver::name_server::name_server_pool][DEBUG] sending request: [Query { name: Name("push.bitwarden.com"), query_type: A, query_class: IN }]
[2023-08-19 16:10:37.568][trust_dns_resolver::name_server::name_server][DEBUG] reconnecting: NameServerConfig { socket_addr: 127.0.0.11:53, protocol: Udp, tls_dns_name: None, trust_nx_responses: false, bind_addr: None }
[2023-08-19 16:10:37.568][trust_dns_proto::xfer][DEBUG] enqueueing message:QUERY:[Query { name: Name("push.bitwarden.com"), query_type: A, query_class: IN }]
[2023-08-19 16:10:37.568][trust_dns_proto::udp::udp_client_stream][DEBUG] final message: ; header 15325:QUERY:RD:NoError:QUERY:0/0/0
; query
;; push.bitwarden.com. IN A
[2023-08-19 16:10:37.568][trust_dns_proto::udp::udp_stream][DEBUG] created socket successfully
[2023-08-19 16:10:37.569][trust_dns_proto::udp::udp_client_stream][DEBUG] received message id: 15325
[2023-08-19 16:10:37.569][trust_dns_resolver::error][DEBUG] Response:; header 15325:RESPONSE:RD,RA:NoError:QUERY:2/0/0
; query
;; push.bitwarden.com. IN A
; answers 2
push.bitwarden.com. 56 IN A 104.18.12.33
push.bitwarden.com. 56 IN A 104.18.13.33
; nameservers 0
; additionals 0
[2023-08-19 16:10:37.569][trust_dns_resolver::error][DEBUG] Response:; header 15325:RESPONSE:RD,RA:NoError:QUERY:2/0/0
; query
;; push.bitwarden.com. IN A
; answers 2
push.bitwarden.com. 56 IN A 104.18.12.33
push.bitwarden.com. 56 IN A 104.18.13.33
; nameservers 0
; additionals 0
[2023-08-19 16:10:37.868][trust_dns_proto::xfer::dns_exchange][DEBUG] io_stream is done, shutting down
[2023-08-19 16:10:37.868][response][INFO] (delete_cipher_put) PUT /api/ciphers/<uuid>/delete => 200 OK
and
[2023-08-19 16:14:13.603][reqwest::connect][DEBUG] starting new connection: https://push.bitwarden.com/
[2023-08-19 16:14:13.604][trust_dns_proto::xfer::dns_handle][DEBUG] querying: push.bitwarden.com A
[2023-08-19 16:14:13.604][trust_dns_resolver::name_server::name_server_pool][DEBUG] sending request: [Query { name: Name("push.bitwarden.com"), query_type: A, query_class: IN }]
[2023-08-19 16:14:13.604][trust_dns_resolver::name_server::name_server][DEBUG] reconnecting: NameServerConfig { socket_addr: 127.0.0.11:53, protocol: Udp, tls_dns_name: None, trust_nx_responses: false, bind_addr: None }
[2023-08-19 16:14:13.604][trust_dns_proto::xfer][DEBUG] enqueueing message:QUERY:[Query { name: Name("push.bitwarden.com"), query_type: A, query_class: IN }]
I have changed nothing and it has just started working…restarted the container to disable debug and its stopped. Will give it another 20 mins and see if it magically starts working again…watch this space.
No longer working again 
I have checked the devices table in the database and I do have the following:-
push_token
refresh_token
push_uuid
Still nothing in the app though unless I open and refresh
Not sure if this is accurate or not but if bitwarden is running in the background push seems to work, if its closed then it fails. Does this sound correct, I am using iOS?