Notifications — (web_files) GET — => 404 Not Found

Can someone help me what the 404 messages mean? Everything else seems to be working fine. This is a self-hosted Vaultwarden docker instance from the testing branch. I have hidden the token value as I wasn’t sure if it’s sensitive.

|                        Starting Vaultwarden                        |
|                      Version 1.28.1-9e5b049d                       |
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
| or        |
|                             |
| Report suspected bugs/issues in the software itself at:            |
|            |
[INFO] Using saved config from `data/config.json` for configuration.
[WARNING] The following environment variables are being overriden by the config.json file.
[WARNING] Please use the admin panel to make changes to them:
[2023-05-20 11:46:33.963][start][INFO] Rocket has launched from
[2023-05-20 11:47:41.789][request][INFO] GET /admin
[2023-05-20 11:47:41.795][response][INFO] (admin_page) GET /admin/ => 200 OK
[2023-05-20 11:47:43.903][request][INFO] GET /admin/logout
[2023-05-20 11:47:43.904][response][INFO] (logout) GET /admin/logout => 303 See Other
[2023-05-20 11:47:43.912][request][INFO] GET /admin
[2023-05-20 11:47:43.913][response][INFO] (admin_page) GET /admin/ => 401 Unauthorized
[2023-05-20 11:47:45.324][request][INFO] POST /admin
[2023-05-20 11:47:45.815][response][INFO] (post_admin_login) POST /admin/ => 200 OK
[2023-05-20 11:47:57.096][request][INFO] GET /admin
[2023-05-20 11:47:57.102][response][INFO] (admin_page) GET /admin/ => 200 OK
[2023-05-20 11:48:13.373][request][INFO] GET /admin
[2023-05-20 11:48:13.378][response][INFO] (admin_page) GET /admin/ => 200 OK
[2023-05-20 11:48:30.572][request][INFO] POST /admin/config
[2023-05-20 11:48:30.573][response][INFO] (post_config) POST /admin/config => 200 OK
[2023-05-20 11:48:32.242][request][INFO] GET /admin
[2023-05-20 11:48:32.248][response][INFO] (admin_page) GET /admin/ => 200 OK
[2023-05-20 11:48:59.638][request][INFO] GET /notifications/hub?access_token=<value hidden by poster>
[2023-05-20 11:48:59.639][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
[2023-05-20 11:49:07.534][request][INFO] GET /notifications/hub?access_token=<value hidden by poster>
[2023-05-20 11:49:07.534][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found
[2023-05-20 11:49:16.288][request][INFO] GET /admin/users/overview
[2023-05-20 11:49:16.312][response][INFO] (users_overview) GET /admin/users/overview => 200 OK
[2023-05-20 11:49:17.693][request][INFO] GET /admin
[2023-05-20 11:49:17.698][response][INFO] (admin_page) GET /admin/ => 200 OK
[2023-05-20 11:49:27.477][request][INFO] GET /admin/diagnostics
[2023-05-20 11:49:30.841][response][INFO] (diagnostics) GET /admin/diagnostics => 200 OK

Either check your reverse proxy logs or enable debug log level to see the specific.

You can also use the F12 developer console of the browser to see what returns a 404.

But, as long as the web-vault works i think i should be fine.

Thanks, it seems there is an issue with Synology’s DSM 7 built-in reverse proxy and I can’t get websockets to work with it.

I’ve set up a Cloudflare tunnel and it works fine on my desktop (ie. the error message goes away) but my iPhone/iPad just crashes when I try to log in to the new Cloudflare reverse proxy. They only work with the reverse proxy that was set up on the Synology :man_shrugging:

I’m guessing the result is that I won’t have Live Sync between the server and the devices.

did anyone found the solution? I am getting the same and I am using Caddy as the reverse proxy. I think it’s my Caddy reverse proxy configuration. If someone could help, would really appreciate.
Here is my Caddy config (please note that I am really new to Caddy): {
} {
  reverse_proxy http://vaultwarden:80 {
    header_up X-Real-IP {remote_host}
    header_up Upgrade {>Upgrade}
    header_up Connection {>Connection}
    header_up Host {host}

  header {
    X-XSS-Protection "0"
    X-Frame-Options "DENY"
    X-Robots-Tag "noindex, nofollow"
    X-Content-Type-Options "nosniff"

  tls /config/certificate_chain.pem /config/private_key.pem