Firefox is not accepting password

[noctrle]

I'm new to using Deluge and got it up and running yesterday through a Docker app in Unraid.

The issue I'm having is when I enter the default 'deluge' password when accessing the webUI, the dialog box immediately reappears for me to enter my password again. I can successfully use the webUI just fine when opening it through Edge. I have everything set up and working correctly now, but am still unable to access the webUI through Firefox, which is definitely my preferred option over Edge.

Has anyone else run into this issue? I can only find a single issue on github related to this and it was closed due to inactivity. (https://github.com/linuxserver/docker-deluge/issues/182)

[ambipro]

Probably has something to do with cookie settings you have, or an Adblocker maybe refusing cookies. Do you use any of those? If so try it with the deluge webui page exempted.

[noctrle]

I have cleared cookies and disabled uBlock Origin, the only extension I had running. I've exempted everything in the browser that would come from my server IP. I've also installed LibreWolf and have the exact same issue with that browser. It's a fork of Firefox, so not sure if this is some kind of issue with Firefox and the compatibility with Deluge. This is strangely the first issue I've had with Firefox after switching back to it like 3-4 years ago.

[ambipro]

I use waterfox (firefox fork) and do not have any issues with this, I'd check to make sure your cookie policies are standard and not strict or something.

[ambipro]

Just as a further way to check, if you use the inspect function (also known as developer tools) - you can watch the "Network" traffic, and see what response you are getting when you enter the password.

You should see a POST to the "json" endpoint - this will have the request be "{"method":"auth.login","params":["deluge"],"id":10}" - and the response will be {"result": true, "error": null, "id": 10} if you successfully logged in. Your browser should then set a cookie for "_session_id" - you can go to "Storage" and see the cookies set for that site there.

(You may have to switch the raw toggle in the response/request view pane to see it as raw JSON - otherwise it will be parsed)

Hopefully this makes sense

[noctrle]

I can't get the raw information as you described above. When I click 'raw' in the header options, it just changes the text color. Digging into these details is new to me, so I apologize if I'm missing something here. This is what I get when using Firefox:



This is what I get with Edge:



There are 7-10 of these same network traffic logs on each browser. Just taking an uneducated look at this, the Edge logs are showing a _session_id after the first request and then subsequent traffic logs show the _session_id appended to the cookie request. I see the request from Firefox, but there's never a _session_id response.

I'm confused how this could be a cookie setting issue in Firefox, as this is the first time I've ever had an issue with a cookie from any website or the Unraid server I've been messing with this past week. I'm also confused how it could be on Unraid's side since I can use other browsers and get the request and use Deluge just fine.

I greatly appreciate your help so far digging into this and giving me other places to look for where the issue is coming from.

[ambipro]

These are the two tabs you want.

[ambipro]

What determines if the client (your browser in this case) is authorized is the cookie set _session_id that I mentioned previously, the first thing I want to determine is if the authorization is being accepted or not.

You will see exactly what is being sent and returned in the above two tabs. It will be a good way into the loading of the page, but it shouldn't be too hard to find - there were 10 POSTs done before my auth login, so just check them until you find it (you will have to attempt to login before doing this)

[noctrle]

Got it, thanks!

This is the Request/Response from the first log:




This is the Request/Response from the second log:

[ambipro]

If you go to the Headers tab in the auth.login query, you should see a Set-Cookie value in the response header, that would contain the cookies your browser is supposed to set to be authorized.

OK, now go to the storage section instead of the network and see if there is a _session_id cookie set at all.

Those cookies should be in the Cookies list of the "main" Storage section under the domain you are using.