Unable to create first user: No matching routes for POST /identity/accounts/register

Hi,
I’m currently trying to set up vaultwarden with nginx reverse proxy. The service seems to start properly and I’m able to access the start page via nginx. However, when creating trying to create the first user, I get an 404 error message as unrendered HTML in the top right corner.

In the log, I can see that /identity/accounts/register is not available, even though I have enabled user signup in the env file.

Dec 17 23:25:09 vaultwarden vaultwarden[1526]: [2022-12-17 23:25:09.190][request][INFO] POST /identity/accounts/register
Dec 17 23:25:09 vaultwarden vaultwarden[1526]: [2022-12-17 23:25:09.190][_][ERROR] No matching routes for POST /identity/accounts/register application/json.
Dec 17 23:25:09 vaultwarden vaultwarden[1526]: [2022-12-17 23:25:09.190][_][WARN] Responding with registered (not_found) 404 catcher.
Dec 17 23:25:09 vaultwarden vaultwarden[1526]: [2022-12-17 23:25:09.190][response][INFO] 404 Not Found

To me it looks like there is still something wrong with the redirection, but I have no idea where to look anymore. nginx error log is empty.

Below you can find my configuration for vaultwarden and the nginx server, which is based on the proxy examples.

vaultwarden.env

# grep -v ^# /etc/vaultwarden.env | grep -v ^$ 
DATA_FOLDER=/var/lib/vaultwarden
WEB_VAULT_FOLDER=/usr/share/webapps/vaultwarden-web/
WEB_VAULT_ENABLED=true
SIGNUPS_ALLOWED=true
DOMAIN=https://vaultwarden.local/
ROCKET_LIMITS={json=10485760}

nginx config

server {
  listen 192.168.178.33:80;
  server_name           vaultwarden.local;
  access_log            /var/log/nginx/vaultwarden.local.access.log;
  error_log             /var/log/nginx/vaultwarden.local.error.log;

  location / {
    return 301 https://$host$request_uri;
  }
}
server {
  listen       192.168.178.33:443 ssl http2;
  server_name  vaultwarden.local;
  ssl_certificate           /etc/nginx/ssl/vaultwarden.local.crt;
  ssl_certificate_key       /etc/nginx/ssl/vaultwarden.local.key;

  index  index.html index.htm index.php;
  access_log            /var/log/nginx/ssl-vaultwarden.local.access.log;
  error_log             /var/log/nginx/ssl-vaultwarden.local.error.log;


  location / {
    proxy_http_version 1.1;
    proxy_set_header "Connection" "";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass http://127.0.0.1:8000;
  }
}

What exactly am I missing here? Can somebody help me to get the issue resolved?

Thanks!

Looks like you are mixing incompatible server and web-vault.
The 1.26.0 version of Vaultwarden only supports up until 2022.10.2.
The current testing tagged images based upon the main branch should support 2022.12.0.

That’s it. I wasn’t thinking about that. Thank you very much for the quick help!