Updated to latest and broken at reverse proxy layer

While trying to fix smtp issues I updated to the latest docker image (1.32.1) and now nothing is working.

Trying to get the log as reported by docker clean I have now set a proper encrypted admin token, and removed the env overrides in the docker command. Which now looks like:

docker run -d --name vaultwarden \
         -v /home/gareth/docker/vaultwarden/data3/:/data/ \
         -p 172.16.69.11:8989:80 \
         -e LOG_LEVEL=info -e EXTENDED_LOGGING=true \
         vaultwarden/server:latest

Behaviour is that attempting to access the webui gives me 404 errors that I can only see in the nginx log, while poking the firefox plugin gives 404 errors that I can see in the docker log. eg:

> docker logs vaultwarden --follow
/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.32.1                           |
|--------------------------------------------------------------------|
| 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:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[INFO] Using saved config from `data/config.json` for configuration.

[2024-10-13 11:21:46.264][start][INFO] Rocket has launched from http://0.0.0.0:80
[2024-10-13 11:22:01.996][request][INFO] POST /identity/connect/token
[2024-10-13 11:22:01.996][response][INFO] 404 Not Found
[2024-10-13 11:22:02.014][request][INFO] POST /identity/connect/token
[2024-10-13 11:22:02.014][response][INFO] 404 Not Found
[2024-10-13 11:22:02.091][request][INFO] POST /identity/connect/token
[2024-10-13 11:22:02.091][response][INFO] 404 Not Found
[2024-10-13 11:22:02.134][request][INFO] POST /identity/connect/token
[2024-10-13 11:22:02.134][response][INFO] 404 Not Found
[2024-10-13 11:22:02.281][request][INFO] GET /icons/vaultwarden.discourse.group/icon.png
[2024-10-13 11:22:02.281][response][INFO] 404 Not Found

My nginx config for the reverse proxy is:

upstream vaultwarden {
        server          172.16.69.11:8989;
}

server {
        access_log /var/log/nginx/vaultwarden.access.log;
        error_log  /var/log/nginx/vaultwarden.error.log error;


    listen       443 ssl;
    server_name  bitwarden.*;
    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

    ssl_session_cache    shared:SSL:1m;
    ssl_session_timeout  5m;

    ssl_ciphers  HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers  on;

    location / {
        proxy_pass http://vaultwarden;
    }

    ssl_certificate /etc/letsencrypt/live/<domain>/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/<domain>/privkey.pem; # managed by Certbot
}

Any clues?