## Using a Sub Path Config
# Path to the root of your installation
# Be sure to DO ADD a trailing /, else you will experience issues
# But only for this location, all other locations should NOT add this.
location/vault/{proxy_http_version1.1;proxy_set_header"Connection""";proxy_set_headerHost$host;proxy_set_headerX-Real-IP$remote_addr;proxy_set_headerX-Forwarded-For$proxy_add_x_forwarded_for;proxy_set_headerX-Forwarded-Proto$scheme;proxy_passhttp://vaultwarden-default;}
@BlackDex commented on GitHub (Jun 23, 2023):
Looks like you configured Vaultwarden to use a sub-path.
I just tested this, and works just as it should.
I think you might have some issues on the reverse proxy config.
Make sure you have the correct config and read the notes.
See: https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples
And specifically:
```nginx
## Using a Sub Path Config
# Path to the root of your installation
# Be sure to DO ADD a trailing /, else you will experience issues
# But only for this location, all other locations should NOT add this.
location /vault/ {
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://vaultwarden-default;
}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Alsan on GitHub (Jun 23, 2023).
Subject of the issue
/api/sync returns 'HTTP/1.1 404 Not Found'.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Install method: Docker image
Clients used: web vault
Reverse proxy and version: nginx/1.23.1
MySQL/MariaDB or PostgreSQL version: no
Other relevant details:
Steps to reproduce
Expected behaviour
Work as expected
Actual behaviour
Resource not found
Troubleshooting data
@BlackDex commented on GitHub (Jun 23, 2023):
Looks like you configured Vaultwarden to use a sub-path.
I just tested this, and works just as it should.
I think you might have some issues on the reverse proxy config.
Make sure you have the correct config and read the notes.
See: https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples
And specifically: