Hi, I have found a possible solution to part of this bug. At ~/.aMule/remote.conf, setting the web interface port to -1 makes the web interface port be 65535. This breaks with the old "standard", which was that when setting -1 for the amuleweb port, it would mean "The port used for External Connections minus one".
Port=-1 is the default configuration obtained when: 1. installing amule-daemon 2. running amuled --ec-config 3. running amuleweb --write-config This used to create the configuration to have amuled listen on port 4712 and amuleweb listen on port 4711 (accessible via http://localhost:4711 ). Now amuleweb listens on port 65535 with this default config, which is undocumented anywhere (e.g., http://www.amule.org/wiki/index.php/HowTo_get_aMule_web_interface#Connecting_from_your_web_browser). Changing the amuleweb port from -1 to the specific wanted port at ~/.aMule/remote.conf solves this. I think that either the default behaviour for the config-generation commands or going back to the old standard should be thought of. Anyway, there is still no command prompt for amuleweb. I don't know if this is a new "feature", but if it is so, it feels strange to read: -------------------------------------- | aMule Web Server | -------------------------------------- Use 'Help' for command list ...and not getting any result when typing any command. Regards, Pitxyoki
