Print

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

[zedder]

hi all again
my amule web server  runs fine inside my lan
but externally i get always timeout  connection.
i have firewall but the port 4711 is open

have you an ideas about this?

thanks
Z

[zedder]

a note:
i'm on suse 9.0 es
are possible some problem whit firewall and correalation whit speed?
thanks

[stefanero]

well 1st of all, maybe for test reasons disable your firewall and see if it works now

SuSEfirewall stop

if it works then, your firewall is missconfigured, if it still does nto work, we can check your setup..
stefanero

[zedder]

my firewall seems down
really i don't know how to procede
can you give me some instructions please?

ciao

[konflict]

same problem here running a debian sarge
connection timeout with the web interface
in fact when i laucn amule , i am able to connect the first time to the web server

but second time, and the next ones  i have a timeout

[stefanero]

well guys to debug this you should

1.st run amuleweb in a console and see if its still running, dont run it at startup with amule, otherwise its hard to tell if it crashed in background, and you did not notice....

2.nd try from localhost, if that works use lan

@konflict:
you use vollstreckers debs? since those are known to have problems with webserver anyway

stefanero

[zedder]

seems to me that apache is the problem ( i'm just tring to think a solution)
i can't connect fastly here http://maurovenanzi.dynalias.org/ ( my host)

it was fast on windows  but now on linux is really slow

thanks

[konflict]

hi
regarding installation process i used the sources and configured, make and mke install them

regarding amulweb console , (if i don't ask amule to launch it on startup) then it is able to start fine

konflict@uber:~$ amuleweb -p 9999
Enter password for mule connection:

Creating client...
Now, doing connection....
Using host 'localhost.localdomain' port: 9999
Trying to connect (timeout = 10 sec)...
Succeeded! Connection established to aMule 2.0.1
---------------------------------
|       aMule Web Server        |
---------------------------------
Use 'Help' for command list

Web Server: Started
aMuleweb$
WSThread: Thread started
WSThread: created service
WSThread: created socket listening on :10000

aMuleweb$
aMuleweb$
aMuleweb$


and it works perfectly from a remote web browser then

so the pb is related in amule startup i suppose any idea?
PS: it was working perfectly before i upgrade to 2.0.1, weird isn't it

[stefanero]

@zedder: apache runs on port 80 and amuleweb on port 4711 how should that be related?

@konflict: can you create a remote conf file in your homedir? and add following lines to it....

Code: [Select]

[EC]
Host=localhost
Port=4712
Password=6ab86d2917b6143152aa90fcfcd619ba
[Webserver]
Port=4000
Template=default
UseGzip=1
AllowGuest=0
AdminPassword=6AB86D2917B6143152AA90FCFCD619BA
GuestPassword=
PageRefreshTime=120
GraphHeight=149
GraphWidth=500
GraphScale=3
just edit it a little and fit it to your needs, rememebr the passwords have to be md5sum...
if you have all setup save this file, and restart amuleweb with amule.
and tell me if that fixed your problem or not

stefanero

[konflict]

sorry stephanero i am not sure i got all of what you told me


 are you asking me to create a new file in my home (let's say named toto)with editing it with the parameters above(with my own modifs)

but if i do so, how will amule know that he should check this file?



anyway here is what i have done
i have created a file named conf-amule.conf  in my home
here it is(as you can see i modified webaccess port to 10000 and tcp local port to 9999, and password)



konflict@uber:~$ more conf-amule
[EC]
Host=localhost
Port=9999
Password=981f1875779561e79585a2ae43a196fb
[Webserver]
Port=10000
Template=default
UseGzip=1
AllowGuest=0
AdminPassword=981f1875779561e79585a2ae43a196fb
GuestPassword=
PageRefreshTime=120
GraphHeight=149
GraphWidth=500
GraphScale=3


then i shut down my manually launched webserver(amuleweb),  configured my amule to launch webserver at startup and restarted again
and OMG
it works
i don't understand but it seem to work indeed

do you have an explanation? it is quite surprising....what should i do at the next patch if it happens again?

anyway thanks for your support, i appreciate that a lot, thats very kind from you to help

konflict

[stefanero]

its a NEW file with the name --> remote.conf

and paste all my setting in it, but then edit them to your needs....amuleweb will automatically read that file on startup, thats why it has to be excat that name and place.

np about the support

[konflict]

oups sorry steph , you answered too fast, i was just editing my previous post

so indeed it is working even with my conf-amule.conf
impressive
thanks a million anyway

but can you explain a little bit what was wrong with my stuff, and how i could prevent it to happen again?

[stefanero]

well...
it works now also when you start amuleweb WITH amuled right? and that did not work before?

usually amuleweb gets its infos from remote.conf and if that is not present it looks in amule.conf....so maybe there is still a little error in the "lookup" process...I will have to ask gonszotopi about that.

but I cannot see any error in your setup, if all your setttings are also right in your amule.conf file, I dont know where the problem was in the 1st place.

stefanero

PS. for finding out how it works with the remote.conf you can use the man pages...
man amuleweb
should work

[Gomaaz]

yeaH starting amule and automatically amuelweb would be great  :baby:

[thedude0001]

...that's just a matter of going to the prefs, remote controls and there checking "run amuleweb on startup"