-
Notifications
You must be signed in to change notification settings - Fork 198
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
Unable to authenticate #804
Comments
As an added note, this happens also from Firefox mobile sometimes. (i please ask not to reply "just use chrome" :) ) |
It's the same issue reported here: |
More info: i totaly deleted my firefox session and started from a fresh one and the issue persist |
So without having to replicate your setup, in the referenced commit I'm now checking for the 401 status and reloading the page as a result. I'm not sure this will actually help, but I'm not sure what else to do. Many auth layers will send a redirect header to the auth page, which SB will follow (SB's native authentication does this as well as authelia). But in case of a 401... not sure what it should do. I could show an alert, but... what then? You can try this out on the edge builds: https://community.silverbullet.md/t/living-on-the-edge-builds/27 |
That might work i guess, but since i am on bare metal i cannot test a docker build right away, maybe you can share a ubild or i will wait until the commit makes to releases |
AFAIK you can use: |
I've just updated the linked instructions for edge (https://community.silverbullet.md/t/living-on-the-edge-builds/27) to also include how to run this with straight Deno without using Docker. |
things have improved, it might be fixed but i need some more time to test. |
I run Silverbullet behind a NGINX reverse proxy that provides SSL + authentication. I use firefox on all my systems (latest release, 123.0.1 )
Works fine in Chrome, but that's not the point. In my experience this issue could be caused by cached files on the client, which seems to be the issue. Usually tough, at the first request the browser auth windows is displayed, not in this case.
I can provide access to my server if needed to repeat the issue (but in private, ofc).
The text was updated successfully, but these errors were encountered: