just thought that i would post up a little problem i was having with the webgui and what i finally did to fix it

i was having problems with the webgui logging me out every time i clicked on anything. if i pressed refresh, start all, stop all, submit settings, etc. it would kick me back out to the login screen and most times the selected action would not be accomplished.

the solution, just delete the cookies for the ktorrent connection from your browser. this solution has seemed to work just fine for my testing thus far.

thank you to everyone who works on ktorrent, it is an awesome product, also if anyone who reads would post up some other keywords to make this more searchable to anyone who has the same problem

Thanks for the tip, but I wonder why does it happen? Well, good to know the solution anyway.

This would mean that your browser is sending the wrong cookie (or we are giving the wrong cookie)

Update:

After using the ktorrent webgui for a few weeks now I have narrowed down the symptoms considerably. The problem seems to only happen after I have remotely accessed "Webmin" for the same computer. It seems that Webmin leaves a couple cookies on my computer that somehow conflict with the ktorrent webgui. Being that I rarely access Webmin after the computer is setup the problem it poses with ktorrent is minimal.

I am using ktorrent v2.1.2 and Webmin v1.330 both with Slackware 11.0 and fluxbox.

We will change the cookie from the rather generic SESSID to something KT specific like KT_SESSID, that should resolve the conflict.

It seems that both of the cookies given by Webmin are conflicting with the ktorrent.

From Firefox the little bit of data on the cookies is as follows

ktorrent's cookie

Name: SESSID
Content: 1737340784
Host: 192.168.1.160
Path: /
Send For: Any type of connection
Expires: at end of session

Webmin's initial cookie (This is given at the login page)

Name: testing
Content: 1
Host: 192.168.1.160
Path: /
Send For: Any type of connection
Expires: at end of session


Webmin's second cookie (This is given after you have logged in)

Name: sid
Content: "some big long hex value"
Host: 192.168.1.160
Path: /
Send For: Any type of connection
Expires: at end of session


Both cookies remain on the computer after using Webmin until I remove them. Also the presence of either of the cookies seems to cause problems with ktorrent. I'm not sure if this helps you guys any, but I figured I would post it.

Same specs as before with a change to v2.1.3

SESSID has now been changed to KT_SESSID, so this should not conflict anymore with webmin, the fix will be part of our next release.

Glad someone finally sussed this out.
My personal variation of the problem was coming from a clash with Ampache. When I deleted all cookies from my IP, I got ktorrent working. I guess it will be fine with the new session ID.

Is that something we can fix quickly ourselves or should we wait for the next release?

Is this fixed in the upcoming 2.2 only?? Because I have updated to 2.1.4 from 2.1.3 and it is still being sent/saved as SESSID. Or is there something that I didn't clear/delete to have it change when I updated??

The fix was not merged to the 2.1 branch and so wasn't included in 2.1.4, it seems I forgot to include this fix when I prepared the 2.1.4 release.

So I got bored and installed the latest svn according to the instructions listed here http://ktorrent.org/index.php?page=faq which according to "ktorrent -v" is version 2.2dev.

Anyway the ktorrent cookie looks to have been updated to KT_SESSID, however the same problem still exists with Webmin interfering with it. I have updated Webmin to the latest version 1.340 and the problem still exists.

This problem is really more of a nuisance than anything so if you can't find a way to fix it don't worry about it.

You probably just need to get rid of old cookies, it would surprise me that webmin is using KT_SESSID.