aMule Forum
English => aMule Help => Topic started by: halsi on July 21, 2004, 03:23:26 PM
-
I run as root => amuleweb... then see....
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This is amuleweb (WebInterface)
Enter password for mule connection (return if no pass defined):
Creating client...
Now doing connection...
Using host localhost port 4712
Trying to connect (timeout = 10 sec) ...
Succeeded ! Connection established
---------------------------------
| aMule Web Server |
---------------------------------
Use 'Help' for command list
Web Server: Started
amuleweb$
WSThread: Thread started
WSThread: created service
WSThread: created socket listening on :0
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
This is a part of my .eMule file !!! Please help me ... THANKS !!!!
[WebServer]
Password=9a7e95ee7e7d9a898e3189844da6e4ee
PasswordLow=fe8ee7ffaa6294962a1800932c7bb7f2
Port=4711
Enabled=1
UseGzip=1
UseLowRightsUser=0
PageRefreshTime=120
[ExternalConnect]
AcceptExternalConnections=1
ECUseTCPPort=1
ECPort=4712
ECPassword=
DlgTabsOnTop=0
UseSecIdent=1
IpFilterOn=1
UseSrcSeeds=0
ShowProgressBar=1
ShowPercent=0
ExtractMetaDataTags=0
FullChunkAlloc=0
FullPartAlloc=0
I don't understand why my webserver doesn't work... I only can start him at the same time as I close my amule. Otherwise it reacts like this:
#amuleweb
This is amuleweb (WebInterface)
Enter password for mule connection (return if no pass defined):
Creating client...
Now doing connection...
Using host localhost port 4712
Trying to connect (timeout = 10 sec) ...
Failed ! Unable to connect to the specified host
PLEASE HELP ME !!!
THANKS !!!
-
http://www.amule.org/wiki/index.php/Webserver
looked at it (twice or more if needed) ?
-
hmmmm
problem is that your webserver is started at
port 0
this is of course not the right port...
I havent really found out yet while amuleweb sometimes does this...
try to reboot your maschine, start amule and then right away start amuleweb afterwards,
sometimes I noticed taht problem when amule was running to long...
also when you start it / close it, and then start it to fast again the webserver port is not released...
so that amuleweb cant get the port again....
so best is to check if everything works, fresh after restart...
stefanero
-
Hi there,
same problem occured to me only after amule crashed and didn't release the ports used. Only a reboot helped.
Another big problem with the webserver is that it first works fine but gets more and more instable while amule is running. I use the webserver much, but sooner or later i only get to see the loginscreen of it or amule itself crashes. Especially if i browse through other sites in the same browserwindow i used for the webinterface. If i don't use the webinterface amule runs fine. Seems it reacts very sensible to the data passed to it.
Greetings,
PsychoChris
-
thanks for your help ...
after REBOOTING my machine ... everything works fine...
THANK YOU VERY MUCH !!!
PS: With a LINUX OS, I think, I must only reboot, if I change the hostname... *g*
-
well ;)
I am not really sure what is causing the problem with amuleweb,
either RAM or the port no being realeased.
I will check with netstat when it happens again to me ;)