[GH-ISSUE #339] HTTP 403 when accessing organization #187

New issue

Closed

opened 2026-03-03 01:26:29 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 01:26:29 +03:00

Owner

Originally created by @Orybon on GitHub (Jan 14, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/339

Hello,

Each time i click on an organization i get a 403 Error :

Request URL: https:///api/organizations//collections
Request Method: GET
Status Code: 403 Forbidden

I'am using the latest version :

docker images | grep bitwarden
mprasil/bitwarden latest a8c3e85c60fb 2 days ago 90.5MB

I created the organization.

Here are the errors found in my docker log :

bitwarden | [2019-01-14 10:37:41][rocket::rocket][INFO] GET /api/organizations:
bitwarden | [2019-01-14 10:37:41][][INFO] Matched: GET /<p..> (web_files)
bitwarden | [2019-01-14 10:37:41][][ERROR] Response was a non-Responder Err: Os { code: 2, kind: NotFound, message: "No such file or directory" }.
bitwarden | [2019-01-14 10:37:41][][INFO] Outcome: Failure
bitwarden | [2019-01-14 10:37:41][][WARN] Responding with 500 Internal Server Error catcher.
bitwarden | [2019-01-14 10:37:41][_][INFO] Response succeeded.

Originally created by @Orybon on GitHub (Jan 14, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/339 Hello, Each time i click on an organization i get a 403 Error : > Request URL: https://<snip>/api/organizations/<snip>/collections > Request Method: GET > Status Code: 403 Forbidden I'am using the latest version : > docker images | grep bitwarden > mprasil/bitwarden latest a8c3e85c60fb 2 days ago 90.5MB I created the organization. Here are the errors found in my docker log : > bitwarden | [2019-01-14 10:37:41][rocket::rocket][INFO] GET /api/organizations: > bitwarden | [2019-01-14 10:37:41][_][INFO] Matched: GET /<p..> (web_files) > bitwarden | [2019-01-14 10:37:41][_][ERROR] Response was a non-`Responder` `Err`: Os { code: 2, kind: NotFound, message: "No such file or directory" }. > bitwarden | [2019-01-14 10:37:41][_][INFO] Outcome: Failure > bitwarden | [2019-01-14 10:37:41][_][WARN] Responding with 500 Internal Server Error catcher. > bitwarden | [2019-01-14 10:37:41][_][INFO] Response succeeded.

kerem closed this issue

2026-03-03 01:26:29 +03:00

kerem commented

2026-03-03 01:26:30 +03:00

Author

Owner

@dani-garcia commented on GitHub (Jan 14, 2019):

I'm not sure where you get the call to GET /api/organizations, I've never seen that one before. The error you are getting is because that endpoint is not implemented. Can you provide the steps used to reproduce the error?

@dani-garcia commented on GitHub (Jan 14, 2019): I'm not sure where you get the call to `GET /api/organizations`, I've never seen that one before. The error you are getting is because that endpoint is not implemented. Can you provide the steps used to reproduce the error?

kerem commented

2026-03-03 01:26:30 +03:00

Author

Owner

@Orybon commented on GitHub (Jan 14, 2019):

I get the call from the DIV on the right side of the home page. When i follow on of the link to an organization.

I tried this evening with my home computer, i can't reproduce the issue.

So i tracked what is happening on the client side of my work computer (the one i got the error) and it appears that i get a 403 ERROR from the proxy of my work SI.

The error logged previously on server side seems to been unrelated to this issue.

This issue can be closed i think, but i wil investigate later on the root cause of the error logged by the server.

Thank you.

@Orybon commented on GitHub (Jan 14, 2019): I get the call from the DIV on the right side of the home page. When i follow on of the link to an organization. I tried this evening with my home computer, i can't reproduce the issue. So i tracked what is happening on the client side of my work computer (the one i got the error) and it appears that i get a 403 ERROR from the proxy of my work SI. The error logged previously on server side seems to been unrelated to this issue. This issue can be closed i think, but i wil investigate later on the root cause of the error logged by the server. Thank you.

kerem commented

2026-03-03 01:26:30 +03:00

Author

Owner

@mprasil commented on GitHub (Jan 15, 2019):

As per your comment, I'm closing this, but feel free to reopen if you manage to reproduce this in some reliable way.

@mprasil commented on GitHub (Jan 15, 2019): As per your comment, I'm closing this, but feel free to reopen if you manage to reproduce this in some reliable way.

kerem referenced this issue

2026-03-03 02:20:15 +03:00

[PR #190] [MERGED] Update the Invitation workflow documentation #2657