You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When basic auth is enabled on nginx reverse proxy, it breaks Yacht frontend. The login screen returns : Bad Authorization header. Expected value 'Bearer <JWT>'
on login form after submission.
To Reproduce
Steps to reproduce the behavior:
Enable basic authentication on nginx reverse proxy
Open frontend URL
Try to login
See error
Expected behavior
It's expected to run smoothly without error
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 24 Server
Browser Chrome
Yacht Version v0.0.7-alpha-2023-01-12--05
The text was updated successfully, but these errors were encountered:
What docker container are you using for nginx? I run linuxserver/nginx:latest and I would have to check my config for the options I have enabled. But I also dont do Auth through Nginx, I let nginx manage my ssl cert and auth is done in yacht.
What docker container are you using for nginx? I run linuxserver/nginx:latest and I would have to check my config for the options I have enabled. But I also dont do Auth through Nginx, I let nginx manage my ssl cert and auth is done in yacht.
My nginx is not in a container, it comes from CloudPanel installed directly on host OS. It runs very fine without basic auth, my problem is that I want to expose Yacht on the internet but the Yacht login form is insecure, there is no protection layer, 2FA or capcha to avoid bruteforce, so I would like to use basic auth or any other protection layer to protect it.
I have had this exact issue in the past, but with treafik and basic auth instead of nginx.
It took me a while to find the solution, but eventually discovered that you need to make sure the Authorization header is not being forwarded by your proxy to Yacht.
In traefik this can be done using removeHeader in the basic auth middleware configuration options (docs here).
How you doing this in nginx I am not sure, but if feel pretty certain if you do this, your issue will be resolved.
Describe the bug
When basic auth is enabled on nginx reverse proxy, it breaks Yacht frontend. The login screen returns
: Bad Authorization header. Expected value 'Bearer <JWT>'
on login form after submission.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It's expected to run smoothly without error
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: