Перейти к основному содержанию

Remote Access

Problems connecting to aMule remotely via amuleapi, amulecmd or amuleweb. For an overview of the remote-control tools, see the Remote Access FAQ.

amulecmd​

I cannot connect to amuled — it doesn't seem to be listening. What's wrong?​

You have probably not enabled External Connections. Open aMule (or amulegui), go to Preferences → Remote Controls, check Accept External Connections, and set a password. The setting is stored in the [ExternalConnect] section of ~/.aMule/amule.conf.

You can also generate the ECPassword hash manually:

echo -n 'yourpassword' | md5sum | cut -d ' ' -f 1

Paste the resulting MD5 hash as the value of ECPassword in ~/.aMule/amule.conf. See amulecmd → Configuration for the full setup.

Connecting from another machine? By default, a new configuration listens for EC connections only on the local machine (ECAddress=127.0.0.1), so only local tools can connect; a configuration created by an older version keeps its previous value (usually empty = all interfaces). For remote access, set ECAddress to the machine's LAN IP address, or leave it empty to listen on all interfaces. Also make sure the EC port (4712 by default) is reachable: see Ports used by aMule and the Firewall guide.

Remote connections​

Why does connecting fail with "Could not resolve … to an IPv4 address."?​

The host you gave has no IPv4 (A) record: the remote tools (amulegui, amuleapi, amulecmd, amuleweb) resolve the core's hostname to IPv4 only (see IPv4 only). Use the core's IPv4 address instead, or a hostname that resolves to it. localhost always works: it resolves to 127.0.0.1.

amuleweb​

Why is amuleweb failing to connect?​

Verify that the amuleweb binary and the amuled/amule binary come from the same release. amuleweb and aMule binaries from different releases negotiate the EC protocol version on connect, and a mismatch is rejected with "Invalid protocol version."

If both binaries match, the failure is usually a wrong EC password, host, or port, or External Connections not being enabled on the aMule side — check the amulecmd connection answer above and follow the amuleweb step-by-step setup.

Why do I always get "No password specified, login will not be allowed."?​

This message means the legacy WebUI has no admin password and no guest password set — it is about the web server login, not the EC password used to reach amuled. Without at least one password, amuleweb refuses every login.

To fix it, set the legacy WebUI admin password:

After saving, check the [WebServer] section of ~/.aMule/remote.conf and verify that AdminPassword (and GuestPassword, if you allow guest access) contain a hashed 32-character hexadecimal string, not a plaintext password and not an empty value.

Why does the legacy WebUI keep going back to the login page?​

Try deleting the cookies for the amuleweb domain in your browser. amuleweb tracks logins with an amuleweb_session_id session cookie, and a stale or corrupted cookie from a previous session can cause this loop.

If clearing cookies does not help and the loop happens from the very first login attempt, the cause is usually a missing legacy WebUI password rather than the cookie — see the answer above. Refer to the amuleweb documentation for full setup details.