All /admin/ subpaths give 404 #1854

Closed
opened 2026-02-05 02:01:54 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @Joly0 on GitHub (Feb 14, 2024).

Subject of the issue

Hey guys, i tried to add a new user to my vaultwarden instance, but now all subpaths below /admin give me an 404 error (but a bitwarden one, not a normal browser one). I can access /admin normally, but all other pages like "users" or "organization" dont work.

I think this might be cause of reverse proxy settings, because when i try to access those pages through ip rather than domain, i can access all subpaths just fine, but i am not sure, where my issue is. Also it was working about 1-2 months ago without an issue.

For reverse proxy i am using nginx proxy manager and the /admin config there looks like this:

location /admin {
    set $forward_path "";
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_set_header X-Forwarded-Host $host/admin;
    if ($forward_path = "") {
        rewrite ^/admin(/.*)$ $1 break;
    }
    proxy_pass http://vaultwarden:80;

    allow 10.50.0.0/24;
    deny all;
}

Deployment environment

  • vaultwarden version:
  • Install method: Docker

  • Clients used:

  • Reverse proxy and version: Nginx Proxy Manager (latest)

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @Joly0 on GitHub (Feb 14, 2024). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> Hey guys, i tried to add a new user to my vaultwarden instance, but now all subpaths below /admin give me an 404 error (but a bitwarden one, not a normal browser one). I can access /admin normally, but all other pages like "users" or "organization" dont work. I think this might be cause of reverse proxy settings, because when i try to access those pages through ip rather than domain, i can access all subpaths just fine, but i am not sure, where my issue is. Also it was working about 1-2 months ago without an issue. For reverse proxy i am using nginx proxy manager and the /admin config there looks like this: ``` location /admin { set $forward_path ""; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_set_header X-Forwarded-Host $host/admin; if ($forward_path = "") { rewrite ^/admin(/.*)$ $1 break; } proxy_pass http://vaultwarden:80; allow 10.50.0.0/24; deny all; } ``` ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: Nginx Proxy Manager (latest) * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1854