aMule Forum
English => aMule Help => Topic started by: saulius on November 14, 2006, 10:41:47 AM
-
Installed aMule with dselect on Debian (no GUI). Only daemon. Trying to start web server. When I try to start aMule daemon with command:
amuled
it reports:
saulius@serveris:~$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/saulius/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
*** TCP socket (ECServer) listening on 0.0.0.0:4712
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/saulius/.aMule/Incoming/ shared
and hangs.
When I try to start web server with command:
amuleweb
it reports:
saulius@serveris:~$ amuleweb
This is amuleweb 2.1.3
Creating client...
and it hangs.
I break these hangings with ctrl+c. Maybe someone has an idea what I do wrong (I am beginner in linux).
Thank you in advance.
Here is amule.conf
ProxyName=
ProxyPort=1080
ProxyEnablePassword=0
ProxyUser=
ProxyPassword=
[WebServer]
Enabled=0
Password=
PasswordLow=
Port=4711
UseGzip=1
UseLowRightsUser=0
PageRefreshTime=120
Template=
[ExternalConnect]
AcceptExternalConnections=1
ECAddress=
ECPort=4712
ECPassword=06a23afb91c2f93137b788271c15f398
ShowProgressBar=1
ShowPercent=0
UseSrcSeeds=0
UseSecIdent=1
IpFilterOn=1
[Razor_Preferences]
FastED2KLinksHandler=1
FullQueueSources=0
HighQueueRankingSources=0
HighQueueRanking=1200
AutoDropTimer=240
NoNeededSourcesHandling=2
[SkinGUIOptions]
UseSkinFile=0
SkinFile=
[Statistics]
MaxClientVersions=0
TotalDownloadedBytes=0
TotalUploadedBytes=0
and remote.conf
Locale=
[EC]
Host=localhost
Port=4712
Password=06a23afb91c2f93137b788271c15f398
[Webserver]
Port=-1
Template=php-default
UseGzip=0
AllowGuest=0
AdminPassword=
GuestPassword=
-
Hi saulius!
amuled doesn't hang, this is the desired behaviour of a running amuled. :)
If you don't want to have these not-interactive display, start amuled with the 'amuled -f' command or use 'amuled &'.
Please change the port setting in the remote.conf file to 4712 and insert the md5-hash of a password at least for Adminpassword and tell us if it works now.
-
It still does not work. I made changes as wuischke told. Now it connects to the server ip through port 4712, but the window of the browser stays blank. (if I don't start amuled it says "unable to connect" in a browser). I start amuled as a user.Directory with all files, including amule.conf and remote.conf are in my user directory.
I have a feeling that it might be something with one of these:
1. Something wrong in amule.conf or remote.conf (are below).
2. Something wrong with firewall. But then it probably always would tell me in the browser that "unable to connect", and now when I start amuled it shows a blank page. ???
3. During instalation I missed part
./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon
since I installed it through dselect (Debian).
4. Problem that I am not aware of.
Maybe someone could give me a tip?
Thank you.
amule.conf related part (as I believe related):
[Proxy]
ProxyEnableProxy=0
ProxyType=0
ProxyName=
ProxyPort=1080
ProxyEnablePassword=0
ProxyUser=
ProxyPassword=
[WebServer]
Enabled=1
Password=06a23afb91c2f93137b788271c15f398
PasswordLow=
Port=4712
UseGzip=1
UseLowRightsUser=0
PageRefreshTime=120
Template=
[ExternalConnect]
AcceptExternalConnections=1
ECAddress=
ECPort=4712
ECPassword=06a23afb91c2f93137b788271c15f398
ShowProgressBar=1
ShowPercent=0
UseSrcSeeds=0
UseSecIdent=1
IpFilterOn=1
[Razor_Preferences]
FastED2KLinksHandler=1
FullQueueSources=0
HighQueueRankingSources=0
HighQueueRanking=1200
AutoDropTimer=240
NoNeededSourcesHandling=2
remote.conf:
Locale=
[EC]
Host=localhost
Port=4712
Password=06a23afb91c2f93137b788271c15f398
[Webserver]
Port=4712
Template=php-default
UseGzip=0
AllowGuest=1
AdminPassword=06a23afb91c2f93137b788271c15f398
GuestPassword=06a23afb91c2f93137b788271c15f398
-
OK, as you now start aMuleweb automatically when you start amuled (Enabled=1), there's no need for remote.conf anymore.
But for debugging matters I would disable this and start aMule manually. Then please delete your remote.conf and create a new one with the command:
amuleweb --create-config-from=~/.aMule/amule.conf
Now start amuleweb in a terminal and tell us what happens when you access it (and there's a blank page).
-
I deleted remote.conf file. It did create the new one. But trying to access the webserver I still see blank page. You can try it too, I will leave it on for a while:
http://193.219.66.50:4712/
here is the report from terminal
saulius@serveris:~$ amuleweb --create-config-from=~/.aMule/amule.conf
saulius@serveris:~$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/saulius/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
*** TCP socket (ECServer) listening on 0.0.0.0:4712
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/saulius/.aMule/Incoming/ shared
-
I bet on template