Skip to content
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

Bitwarden Unified - Nginx - Permission denied - Since Update - See Issue 2567 #3817

Closed
1 task done
tk7507 opened this issue Feb 16, 2024 · 3 comments
Closed
1 task done

Comments

@tk7507
Copy link

tk7507 commented Feb 16, 2024

Steps To Reproduce

Updated to bitwarden/self-host:beta

Result:
2023-01-11 15:15:48,962 INFO RPC interface 'supervisor' initialized
2023-01-11 15:15:48,962 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-01-11 15:15:48,963 INFO supervisord started with pid 52

Updated back to bitwarden/self-host:2024.1.2-beta

Working again

Tested workaround of Issue 2567 :
No, result. But Folders were not created

docker exec {Container name} mkdir /var/lib/nginx/tmp/client_body
docker exec {Container name} mkdir /var/lib/nginx/tmp/proxy
docker exec {Container name} mkdir /var/lib/nginx/tmp/fastcgi
docker exec {Container name} mkdir /var/lib/nginx/tmp/uwsgi
docker exec {Container name} mkdir /var/lib/nginx/tmp/scgi

Expected Result

No CRIT fault

Actual Result

CRIT fault

Screenshots or Videos

No response

Additional Context

No response

Build Version

beta

Environment

Self-Hosted

Environment Details

Synology

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@tk7507 tk7507 added the bug label Feb 16, 2024
@djsmith85
Copy link
Contributor

Hi @tk7507 and thank you for your report.

There have been some updates to the dev and beta release, since your report, which have resolved issues (#3755, #3820) and might be related to yours.

Could you please test with the latest release and let us know if this resolves your issue?

Kind regards,
Daniel

Copy link
Contributor

We need more information before we can help you with your problem. As we haven’t heard from you recently, this issue will be closed.

If this happens again or continues to be an problem, please respond to this issue with the information we’ve requested and anything else relevant.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
@markusdeger
Copy link

Sorry, was on vacation. Can confirm that the issue is solved in version bitwarden/self-host:2024.2.2-beta.

Thanks for the support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants