Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GET /api/config --> [response][INFO] (web_files) GET /<p..> [10] => 404 Not Found #4218

Closed
aksharOza opened this issue Jan 1, 2024 Discussed in #3733 · 0 comments
Closed

Comments

@aksharOza
Copy link

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

[2024-01-01 16:10:38.812][request][INFO] GET /api/config
[2024-01-01 16:10:38.812][response][INFO] GET /<p..> [10] (web_files) => 404 Not Found

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.

@aksharOza aksharOza changed the title [response][INFO] (web_files) GET /<p..> [10] => 404 Not Found GET /api/config --> [response][INFO] (web_files) GET /<p..> [10] => 404 Not Found Jan 1, 2024
Repository owner locked and limited conversation to collaborators Jan 1, 2024
@BlackDex BlackDex converted this issue into discussion #4219 Jan 1, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant