-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Admin panel login redirect #1040
Comments
I have a similar problem. |
incorrect nginx reverse proxy configuration
Replace with:
reference https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples Nginx (by shauder) |
I have the issue with apacheand as I can see in the wiki this parameters for nginx already exists. |
The redirect is done based upon the |
In my case is multihost installation in a subfolder and the domain is configured right |
But with multi host you can only configure one host/domain in the config. And that is where the Redirect is pointing you to. |
Closing this ticket because of inactivity. |
I still have the issue, so I don't know how to keep the discussion moving on as the problem persist. |
Well i have tested this my self just right now, and i can't reproduce this issue. Also, i saw that there was no example for nginx available at the Proxy Examples, so i added this. |
@Mte90 did you also added the correct sub-path into the DOMAIN variable? So like |
Hey, to continue on that one.. I used the apache2-sublocation stencil from the wiki - which does not mention However A simple Entering the correct password results in first a POST (with a set token), next a 303, then again a GET on the Setting |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Subject of the issue
Hi,
I am using a Bitwarden_RS instance on my personal host behind a nginx reverse proxy for HTTPS. Let's Encrpyt. All that good stuff. Now i am looking into hardening my installation before i go live. As part of that I configured my nginx to block every public access to the /admin/ subdirectory.
This works like intended. If i try to access
https://bitwarden.public.dns/admin
i am greeted with a 403 warning. So far so good.I am still able to access the admin panel locally by accessing
https://bitwarden.local/admin
. Now i enter my token and pressenter
. Then i get redirected tohttps://bitwarden.public.dns/admin
and receive a 403. If i change the address tohttps://bitwarden.local/admin
again i can use the admin panel without problems.The same thing happens when i log out of the admin panel (although it does not bother me in that case).
Is it possible to stop that redirecting to the public dns after login? After all it is just for convenience.
Great project! Love it!
SinTh0r4s
My environment
The text was updated successfully, but these errors were encountered: