aMule Forum

English => en_Bugs => Topic started by: Dante_ on September 13, 2005, 12:20:08 PM

Title: amuleweb not working in any IP outside 192.168.X.X
Post by: Dante_ on September 13, 2005, 12:20:08 PM

Amule web works just fine inside my LAN..

To the outside i've forwared the port (4711) and the login page appears and i can login sucessfuly, but after login all the links in the search/transfer/etc buttons are: http://host:4711/# (all of them exepting the logout link, its the only working).

All the links in the page are jus simply pointing to #, but inside the lan the links are correct..
It's not browser probles, because i've used the same laptop inside and outside the LAN.

Is this a stupid "feature" to prevent WAN access!? If it is, how to disable it?
Any host outside the Subnet Mask of the machine running amule gets this # links..  ;(

Title: Re: amuleweb not working in any IP outside 192.168.X.X
Post by: stefanero on September 13, 2005, 12:42:44 PM

hum
works fine here, inside and outside lan

what template are you using? default? ot chicane template?

Title: Re: amuleweb not working in any IP outside 192.168.X.X
Post by: Dante_ on September 13, 2005, 06:13:52 PM

chicane.. i'm going to try the defualt then.. but is not as near as pleasant to my eyes  :(

Title: Re: amuleweb not working in any IP outside 192.168.X.X
Post by: lfroen on September 13, 2005, 07:25:26 PM

Please check php version of amuleweb. just add --php switch to command line (works with cvs snapshots only).

Title: Re: amuleweb not working in any IP outside 192.168.X.X
Post by: Dante_ on September 14, 2005, 12:11:44 PM

Well, it appears to happen only when using amuleweb trough a Squid Proxy at my campus... On a friend DSL line connecting directy it works just fine!
Squid at the campus reports to be "squid/2.5.STABLE10-20050524" ...
Now I dont know if it is a bug with squid or with amuleweb..  ?(

Title: Re: amuleweb not working in any IP outside 192.168.X.X
Post by: stefanero on September 14, 2005, 01:56:00 PM

well of course squid ;)
dont know how restrictive the squid is setup, they might filter some things...

maybe you can try to add your webserver as a virtuell host in an apache on port 80, and see if you can it this way to work.