Originally created by @UltraBlackLinux on GitHub (Aug 27, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2710
<!--
# ###
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
Whenever I try to edit an item or folder (moving, renaming, whatever) I get [this error](https://github.com/dani-garcia/vaultwarden/files/9438128/-1661609993223.log). The only thing that works is creating an entry
### 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: latest
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: docker image
* Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Web vault, desktop
* Reverse proxy and version: <!-- if applicable --> nginx version: nginx/1.18.0 (Ubuntu)
* MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> none (I didn't change anything at least)
* Other relevant details: I'm using firewalld and just imported my whole KeePassXC config via the KeePassX import option.
### 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? -->
I started the vaultwarden container as advised in the wiki
### Expected behaviour
<!-- Tell us what you expected to happen -->
Editing anything should work
### Actual behaviour
<!-- Tell us what actually happened -->
Everytime I try to edit or create anything I get the error mentioned above. Creating new passwords works
### Troubleshooting data
<!-- Share any log files, screenshots, or other relevant troubleshooting data -->
[-1661609993223.log](https://github.com/dani-garcia/vaultwarden/files/9438128/-1661609993223.log)
Could you provide logs from Vaultwarden?? The logs attached aren't useful, these look like client logs, and that is not something on the Vaultwarden side we can fix.
Also check the nginx logs.
<!-- gh-comment-id:1229204331 -->
@BlackDex commented on GitHub (Aug 27, 2022):
Could you provide logs from Vaultwarden?? The logs attached aren't useful, these look like client logs, and that is not something on the Vaultwarden side we can fix.
Also check the nginx logs.
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Could you provide logs from Vaultwarden?? The logs attached aren't useful, these look like client logs, and that is not something on the Vaultwarden side we can fix.
Also check the nginx logs.
I thought so, but I couldn't get my hands on any useful logs. The only ones I'm seeing are login logs
EDIT: Almost forgot the nginx logs: it doesn't look like any recent errors exist in there, and the access log shows my deletion attempt
<!-- gh-comment-id:1229205587 -->
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
> Could you provide logs from Vaultwarden?? The logs attached aren't useful, these look like client logs, and that is not something on the Vaultwarden side we can fix.
>
> Also check the nginx logs.
I thought so, but I couldn't get my hands on any useful logs. The only ones I'm seeing are login logs
EDIT: Almost forgot the nginx logs: it doesn't look like any recent errors exist in there, and the access log shows my deletion attempt
Could you then try to provide the support string from the admin diagnostics page? (/admin)
<!-- gh-comment-id:1229205827 -->
@BlackDex commented on GitHub (Aug 27, 2022):
Could you then try to provide the support string from the admin diagnostics page? (`/admin`)
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
I can't get the admin page to work. Currently vaultwarden is hosted at domain/vaultwarden/ via proxy_pass - This works perfectly, but the admin panel redirects me to domain/admin which is not the vaultwarden location
Also css seems broken on the admin page. Proxy pass is just not great
EDIT: Managed to access it via the ip directly. This is apparently the default which works.
<!-- gh-comment-id:1229206290 -->
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
I can't get the admin page to work. Currently vaultwarden is hosted at domain/vaultwarden/ via proxy_pass - This works perfectly, but the admin panel redirects me to domain/admin which is not the vaultwarden location
Also css seems broken on the admin page. Proxy pass is just not great
EDIT: Managed to access it via the ip directly. This is apparently the default which works.
Connection to xyz failed: Error during WebSocket handshake: Unexpected response code: 400
Failed to start the connection: Error: There was an error with the transport
<!-- gh-comment-id:1229208826 -->
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Okay! Got it. Took some time to deal with various issues, but here it is:
### Your environment (Generated via diagnostics page)
* Vaultwarden version: v1.25.2
* Web-vault version: v2022.6.2
* Running within Docker: true (Base: Debian)
* Environment settings overridden: true
* Uses a reverse proxy: true
* IP Header check: true (X-Real-IP)
* Internet access: true
* Internet access via a proxy: false
* DNS Check: true
* Time Check: true
* Domain Configuration Check: false
* HTTPS Check: false
* Database type: SQLite
* Database version: 3.35.4
* Clients used:
* Reverse proxy and version:
* Other relevant information:
### Config (Generated via diagnostics page)
<details><summary>Show Running Config</summary>
**Environment settings which are overridden:** ADMIN_TOKEN
```json
{
"_duo_akey": null,
"_enable_duo": false,
"_enable_email_2fa": false,
"_enable_smtp": true,
"_enable_yubico": true,
"_icon_service_csp": "",
"_icon_service_url": "",
"_ip_header_enabled": true,
"admin_ratelimit_max_burst": 3,
"admin_ratelimit_seconds": 300,
"admin_token": "***",
"allowed_iframe_ancestors": "",
"attachments_folder": "data/attachments",
"authenticator_disable_time_drift": false,
"data_folder": "data",
"database_conn_init": "",
"database_max_conns": 10,
"database_timeout": 30,
"database_url": "****/**.*******",
"db_connection_retries": 15,
"disable_2fa_remember": false,
"disable_admin_token": false,
"disable_icon_download": false,
"domain": "****://******.************.**/***********",
"domain_origin": "****://******.************.**",
"domain_path": "/***********",
"domain_set": true,
"duo_host": null,
"duo_ikey": null,
"duo_skey": null,
"email_attempts_limit": 3,
"email_expiration_time": 600,
"email_token_size": 6,
"emergency_access_allowed": true,
"emergency_notification_reminder_schedule": "0 5 * * * *",
"emergency_request_timeout_schedule": "0 5 * * * *",
"enable_db_wal": true,
"extended_logging": true,
"helo_name": null,
"hibp_api_key": null,
"icon_blacklist_non_global_ips": true,
"icon_blacklist_regex": null,
"icon_cache_folder": "data/icon_cache",
"icon_cache_negttl": 259200,
"icon_cache_ttl": 2592000,
"icon_download_timeout": 10,
"icon_redirect_code": 302,
"icon_service": "internal",
"incomplete_2fa_schedule": "30 * * * * *",
"incomplete_2fa_time_limit": 3,
"invitation_org_name": "Vaultwarden",
"invitations_allowed": true,
"ip_header": "X-Real-IP",
"job_poll_interval_ms": 30000,
"log_file": "/data/vaultwarden.log",
"log_level": "Info",
"log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f",
"login_ratelimit_max_burst": 10,
"login_ratelimit_seconds": 60,
"org_attachment_limit": null,
"org_creation_users": "",
"password_hints_allowed": true,
"password_iterations": 100000,
"reload_templates": false,
"require_device_email": false,
"rsa_key_filename": "data/rsa_key",
"send_purge_schedule": "0 5 * * * *",
"sends_allowed": true,
"sends_folder": "data/sends",
"show_password_hint": false,
"signups_allowed": false,
"signups_domains_whitelist": "",
"signups_verify": false,
"signups_verify_resend_limit": 6,
"signups_verify_resend_time": 3600,
"smtp_accept_invalid_certs": false,
"smtp_accept_invalid_hostnames": false,
"smtp_auth_mechanism": null,
"smtp_debug": false,
"smtp_explicit_tls": null,
"smtp_from": "",
"smtp_from_name": "Vaultwarden",
"smtp_host": null,
"smtp_password": null,
"smtp_port": 587,
"smtp_security": "starttls",
"smtp_ssl": null,
"smtp_timeout": 15,
"smtp_username": null,
"templates_folder": "data/templates",
"tmp_folder": "data/tmp",
"trash_auto_delete_days": null,
"trash_purge_schedule": "0 5 0 * * *",
"use_syslog": false,
"user_attachment_limit": null,
"web_vault_enabled": true,
"web_vault_folder": "web-vault/",
"websocket_address": "0.0.0.0",
"websocket_enabled": false,
"websocket_port": 3012,
"yubico_client_id": null,
"yubico_secret_key": null,
"yubico_server": null
}
```
</details>
EDIT: Some client side stuff that I just noticed:
```
Connection to xyz failed: Error during WebSocket handshake: Unexpected response code: 400
Failed to start the connection: Error: There was an error with the transport
```
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Yikes. It seems to be proxy related; Just entering my server ip and directory allows me to delete stuff as expected
I just noticed that I did get some kind of logs from my previous attempt now:
[2022-08-27 15:22:36.817][_][ERROR] No matching routes for GET / text/html.
[2022-08-27 15:22:36.818][_][WARN] No 404 catcher registered. Using Rocket default.
[2022-08-27 15:28:59.691][_][ERROR] No matching routes for POST //identity/connect/token application/x-www-form-urlencoded.
[2022-08-27 15:28:59.691][_][WARN] No 404 catcher registered. Using Rocket default.
I can't log in from the web anymore
EDIT; HUH? My config is causing that? How is that possible
<!-- gh-comment-id:1229212926 -->
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Yikes. It seems to be proxy related; Just entering my server ip and directory allows me to delete stuff as expected
I just noticed that I did get some kind of logs from my previous attempt now:
```
[2022-08-27 15:22:36.817][_][ERROR] No matching routes for GET / text/html.
[2022-08-27 15:22:36.818][_][WARN] No 404 catcher registered. Using Rocket default.
[2022-08-27 15:28:59.691][_][ERROR] No matching routes for POST //identity/connect/token application/x-www-form-urlencoded.
[2022-08-27 15:28:59.691][_][WARN] No 404 catcher registered. Using Rocket default.
```
I can't log in from the web anymore
EDIT; HUH? My config is causing that? How is that possible
It looks like you configured your reverse proxy incorrectly.
Because you are using a sub-path it needs some different configuration they just a default proxy pass.
I suggest to double check the wiki regarding this, and see if your configuration matches. https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples and then check my example Nginx with sub-path.
The reason the admin interface isn't working, is because either the reverse proxy is faulty, or your DOMAIN config variable is incorrect. Once you have fixed your reverse proxy, the admin interface will probably work, and then the web-vault also will work just fine.
<!-- gh-comment-id:1229215782 -->
@BlackDex commented on GitHub (Aug 27, 2022):
It looks like you configured your reverse proxy incorrectly.
Because you are using a sub-path it needs some different configuration they just a default proxy pass.
I suggest to double check the wiki regarding this, and see if your configuration matches.
https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples and then check my example `Nginx with sub-path`.
The reason the admin interface isn't working, is because either the reverse proxy is faulty, or your `DOMAIN` config variable is incorrect. Once you have fixed your reverse proxy, the admin interface will probably work, and then the web-vault also will work just fine.
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 @UltraBlackLinux on GitHub (Aug 27, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2710
Subject of the issue
Whenever I try to edit an item or folder (moving, renaming, whatever) I get this error. The only thing that works is creating an entry
Deployment environment
Install method: docker image
Clients used: Web vault, desktop
Reverse proxy and version: nginx version: nginx/1.18.0 (Ubuntu)
MySQL/MariaDB or PostgreSQL version: none (I didn't change anything at least)
Other relevant details: I'm using firewalld and just imported my whole KeePassXC config via the KeePassX import option.
Steps to reproduce
I started the vaultwarden container as advised in the wiki
Expected behaviour
Editing anything should work
Actual behaviour
Everytime I try to edit or create anything I get the error mentioned above. Creating new passwords works
Troubleshooting data
-1661609993223.log
@BlackDex commented on GitHub (Aug 27, 2022):
Could you provide logs from Vaultwarden?? The logs attached aren't useful, these look like client logs, and that is not something on the Vaultwarden side we can fix.
Also check the nginx logs.
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
I thought so, but I couldn't get my hands on any useful logs. The only ones I'm seeing are login logs
EDIT: Almost forgot the nginx logs: it doesn't look like any recent errors exist in there, and the access log shows my deletion attempt
@BlackDex commented on GitHub (Aug 27, 2022):
Could you then try to provide the support string from the admin diagnostics page? (
/admin)@UltraBlackLinux commented on GitHub (Aug 27, 2022):
I can't get the admin page to work. Currently vaultwarden is hosted at domain/vaultwarden/ via proxy_pass - This works perfectly, but the admin panel redirects me to domain/admin which is not the vaultwarden location
Also css seems broken on the admin page. Proxy pass is just not great
EDIT: Managed to access it via the ip directly. This is apparently the default which works.
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Okay! Got it. Took some time to deal with various issues, but here it is:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
EDIT: Some client side stuff that I just noticed:
@UltraBlackLinux commented on GitHub (Aug 27, 2022):
Yikes. It seems to be proxy related; Just entering my server ip and directory allows me to delete stuff as expected
I just noticed that I did get some kind of logs from my previous attempt now:
I can't log in from the web anymore
EDIT; HUH? My config is causing that? How is that possible
@BlackDex commented on GitHub (Aug 27, 2022):
It looks like you configured your reverse proxy incorrectly.
Because you are using a sub-path it needs some different configuration they just a default proxy pass.
I suggest to double check the wiki regarding this, and see if your configuration matches.
https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples and then check my example
Nginx with sub-path.The reason the admin interface isn't working, is because either the reverse proxy is faulty, or your
DOMAINconfig variable is incorrect. Once you have fixed your reverse proxy, the admin interface will probably work, and then the web-vault also will work just fine.