aMule Forum
English => aMule Help => Topic started by: 05jos on October 03, 2006, 12:42:42 PM
-
Hello! I have Clarkconnect 4.0 community edition. It is based on CentOS 4.2 wich should be comptable with Fedora Core 3. So i used FC3 RPMs to install amule.
I installed packages:
aMule-2.1.3-1_FC3.i586.rpm
aMule-amulecmd-2.1.3-1_FC3.i586.rpm
aMule-daemon-2.1.3-1_FC3.i586.rpm
aMule-webserver-2.1.3-1_FC3.i586.rpm
wx-base-unicode-2.6.3-1.i586.rpm
wx-gtk2-unicode-2.6.3-1.i586.rpm
Everything was installed smoothly. Then I run amuled, because i have no x-server. Stoped it. Configure conf files. Run amuleweb -w to create remote.conf. Edit this file too. And finally run amuled.... Everything ok. amulecmd.... Everithing OK. Amuleweb.... OOPS! Not everything OK.
I can connect to login page and enter password... but then window is divided to three frames and every frame is just a login page again... in few seconds everything go back to to the first step... (one frame; login page)
Output of amuleweb is following:
This is amuleweb 2.1.3
Creating client...
Succeeded! Connection established to aMule 2.1.3
--------------------------------------
| aMule Web Server |
--------------------------------------
Use 'Help' for command list
Web Server: Started
WSThread: Thread started
aMuleweb$ WSThread: created socket listening on :4711
Processing request [original]:
No session opened - will request login
Session created - requesting login
Session is not logged and request have no password
Processing request [redirected]: login.php
No session opened - will request login
Session created - requesting login
No session opened - will request login
Session created - requesting login
Processing request [original]:
No session opened - will request login
Session created - requesting login
Checking password
Password ok
Processing request [redirected]: index.html
Processing request [original]: top.html
No session opened - will request login
Session created - requesting login
Session is not logged and request have no password
Processing request [redirected]: login.php
Processing request [original]: amuleweb-main-dload.php
No session opened - will request login
Session created - requesting login
Session is not logged and request have no password
Processing request [redirected]: login.php
Processing request [original]: footer.php
No session opened - will request login
Session created - requesting login
Session is not logged and request have no password
Processing request [redirected]: login.php
No session opened - will request login
Session created - requesting login
No session opened - will request login
Session created - requesting login
Processing request [original]: footer.php
No session opened - will request login
Session created - requesting login
Session is not logged and request have no password
Processing request [redirected]: login.php
No session opened - will request login
Session created - requesting login
No session opened - will request login
Session created - requesting login
So,... if anyone can help i would be very grateful.
Thx and sorry for my English.
-
I found the problem! YES! :D
It was the line ECAdress...
Now i left it empty and everything works just great! :)
-
I have the same problem and the ECAddress is already empty in my configuration.
In fact it works fine when I connect to amuleweb on the local machine, but I get the exact same symptoms as described above when I connect from a different machine.
Anybody cares to help ? :baby:
Thanks
-
Try to set it to your current IP...
-
No luck. the server is in a local network. I tried to give it the private IP address or the public one (from the ISP) and none of them work. In the second case, I cannot even connect to the webserver.
Also, I found that more than the local machine, if I connect inside the network, it works fine, that seems weird to me.
Thanks for the help.
-
Try deleting the cookies of your browser.
-
I had precisely the problem, I could get as far as amuleweb login screen but on entering the password I had setup, I was presented briefly with three frames before the login screen was displayed again.
What fixed it for me was enabling cookies in my browser (I was kicking myself after realizing this was the problem).
Hope this helps.