Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lukygrl]

Hi,

I am trying to set up the aMule daemon on a Debian Sarge and I have a few questions.

I've configured the amule.conf with my ports (btw, do I have to write just the ports or IP:PORT, the amule help pages seem to say ip and port , but the default file just had the port), and activated to allow external connections and activated the webserver.

Now I type amuled and I get:

*** TCP socket (EC Server) listening on 0.0.0.0:myport
*** Server UDP socket (TCP+3) at 0.0.0.0:myport
.... (and with all ports)
and then it stops at :
....
Servers: Connected

and here it stays , if I try to access the webserver I can't. Am I doing something wrong ? any advice?

Thanks in advanced.  

[thedude0001]

Everything works fine. The webserver amuleweb is not integrated within amule or amuled, it is a standalone application which you have to configure and start on its own. Take a look at the webserver HowTo: http://www.amule.org/wiki/index.php/Webserver

[lukygrl]

Thanks, that quite did it.

Just one more thing. When I turn on the amuleweb it is trying to use:

Using host 'localhost.localdomain' port:####

but it doesn't work, and the port number it is trying it's not the one I have configured in the amule.conf, any ideas why?

I've tried to do:

amuleweb -h "x.x.x.x" -p ####

and the port works but it dosen't get the host.

Any help will be very much appreciated, thanks again. :rolleyes:

[ken]

There are two ways to get amuleweb running: 1) let amuled start it for you, or 2) start it manually yourself.  If you let amuled start it for you (in amule.conf section [WebServer]: Enabled=1), amuled takes care of providing amuleweb with the proper configuration settings as specified in your amule.conf.

However, you are starting it manually.  In this case, amuleweb does not read its configuration from amule.conf.  Instead it reads it either from the command line arguments or from ~/.aMule/remote.conf.  It is done this way because amuleweb might not be running on the same computer as amuled, and so might not have access to amule.conf.

To create remote.conf, the easiest thing to do is tell amuleweb to create it from the settings in amule.conf.  This is the command: amuleweb --create-config-from=~/.aMule/amule.conf

That only needs to be done once to initially create an appropriate remote.conf.  From then on, amuleweb will read its configuration from there.