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 C
Package: amule-daemon
Version: 2.2.1-1
Severity: important
Since the update to 2.2.1, amuleweb stopped working. It connects to
the daemon but then just sits there. The amuleweb prompt does not
appear as in previous versions, no commands are recognized and it isn't
possible to access the webserv
2 matches
Mail list logo
