What is happening → I open my rclone subdomain, authenticate with Authelia, reach the rclone login screen
What should happen → I press Login with empty creds and it works
What happens → I get 302 redirect to my authelia domain.
Weird edge case → If I enter my SSO basic auth creds, I get logged in to rclone.
A log from the command that you were trying to run with the -vv flag
ubuntu@enarvy-server:/data$ ../home/ubuntu/Rclone/rclone-browser.sh
2026/01/03 14:50:41 DEBUG : rclone: Version "v1.72.1" starting with parameters ["rclone" "rcd" "--rc-web-gui" "--rc-addr" ":40404" "--rc-no-auth" "-vv"]
2026/01/03 14:50:46 DEBUG : Current tag: v2.0.5, Release tag: v2.0.5
2026/01/03 14:50:46 NOTICE: Web GUI exists. Update skipped.
2026/01/03 14:50:46 NOTICE: It is recommended to use web gui with auth.
2026/01/03 14:50:46 NOTICE: Serving Web GUI
2026/01/03 14:50:46 NOTICE: Serving remote control on http://[::]:40404/
You’d want to try private/incognito or something as there is probably a cached cookie as it’s doesn’t clear it out. Just hit login without entering anything and you go right in.
Since there were no logs on rclone, I opened my Network tab and found that I am getting a 302 redirect from the login API to my Authelia which is failing due to CORS. What’s weird is that the authelia config is succesfully working on my other websites.
The response has the header - www-authenticate Basic realm="Authorization Required"
I have tried and failed to get this working without exposing the API. When I supply my SSO creds in the rclone form with no-auth enabled, it works but I’d rather not do this because I don’t understand how it’s working.