aMule Forum
English => aMule Help => Topic started by: juanjosaurio on May 03, 2006, 08:12:34 AM
-
Fedora Core 5 updated
Installed using yum, so no compilation required.
After a bit of trouble, managed to get amuled working, and also amuleweb (called from amuled).
I load http://localhost:4711 without problems, type the password, and stay in login screen. Can't get past that. Checked the source and there's no URL in the action field of form. Is it right? What else can be?
Thanks in advance
Juanjo
-
question how do you start amuelweb??
with amule(d) together or seperate?
if with amule(d) together post your amule.conf , if seperate search the forum for "remote.conf" and create one
-
Hi,
I'm having exactly the same probleme since a few days, WHEREAS I used to run amuled with amuleweb without any probleme !!??
I have amule.conf with EC activated and EC password created (the same as in remote.conf)
I'm running aMule 2.1.1 on a Fedora Core 5, the only changes I had on my server were on the apache configuration, is there a link ?
I can't find out what configuration changes (apache, php, any other) resulted in the login web page lock.
Any ideas ?
Tnx in advance.
L0K
-
clear cookies.
-
clear cookies.
Can you do ethereal trace of traffic exchange between browser and amuleweb ?
Or, maybe I can have your cookies file or at least amuleweb relevant line ?
I can't figure out what kind of cookie confuses amuleweb. Example will be very helpful
-
http://forum.amule.org/thread.php?threadid=8987&sid=
aMule has a bug with the cookies
-
I know, but unable to reproduce it and thus can't fix it. I would be very nice to get ethereal trace of cookie file. Or both :)
-
Hi all,
Clearing cookies did worked for me, so THANK YOU.
Before I cleared cookies, i captured ethereal traces from client to server on port 4711 and try to login, so i can send them to you lfroen if it can helps.
I couldn't sent you cookies as i had too manies on my client from that server. Can't the problem come with other applications on the same server using SESSID cookies too ? Can't amuleweb use a custom cookie (php_session) name to control login and avoid such risks ?
lfroen tell me if you want me to send ethereal traces of the loging probleme.
Thanks again.
L0K
-
I think giving the cookie a special name like "amuleweb_cookie" and then simple using that should solve all our cookie issues...
-
lfroen tell me if you want me to send ethereal traces of the loging probleme.
L0K: yes, please send your traces to lfroen@gmail.com - this will be very helpfull !
-
mail sent hope it'll help.
See you.
L0K
-
Thank you, your trace is indeed helpful - now I clearly see the problem (my lack of RFC understanding).
I will fix it in few days.
-
Thanks lfroen! :)
-
:baby:
-
AFAIK, lfroen has already fixed this issue.
-
I am having the same issue again in version 2.1.2. Isn't the fix included in this version yet?
-
Unfortunatly no. Fix exists in development branch only.