Replies: 5 comments 5 replies
-
I've got the same error when calling /api/public/collections |
Beta Was this translation helpful? Give feedback.
-
Check your reverse proxy config, it probably has something configured incorrectly. |
Beta Was this translation helpful? Give feedback.
-
Same result here, in Chrome incognicto mode I am able to login but no logins are shown (doesnt seem to sync) whilst the chrome browser extension is working, same for desktop application and when using edge browser. Emptying all site data and storage for vaultwarden in Chrome doesnt help either. |
Beta Was this translation helpful? Give feedback.
-
Well, pulling new docker image and recreating worked for me |
Beta Was this translation helpful? Give feedback.
-
I am on the latest version and I am getting the same error, able to use it perfectly fine, just when I use the API calls from N8N Bitwarden node, I get this error. Running behind a reverse proxy on Cosmos Cloud! /--------------------------------------------------------------------
[2024-09-05 20:30:52.771][request][INFO] POST /identity/connect/token |
Beta Was this translation helpful? Give feedback.
-
When using the bitwarden CLI, I keep receiving this HTML snippet as part of the response:
Unable to fetch ServerConfig: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>404 Not Found</title> </head> <body align="center"> <div role="main" align="center"> <h1>404: Not Found</h1> <p>The requested resource could not be found.</p> <hr /> </div> <div role="contentinfo" align="center"> <small>Rocket</small> </div> </body> </html>
When looking through the bitwarden container logs I see
I am using an NGINX reverse proxy and in the access log there I see the following:
"GET /api/config HTTP/1.1" 404 266 "-" "Bitwarden_CLI/2023.12.1 (LINUX)"
I would appreciate any assistance to fix my setup so that the 'api/config' resource can be found.
Beta Was this translation helpful? Give feedback.
All reactions