Server setup

Server setup

To use aMule Remote you must enable External Connections (EC) on your amuled.

1. Edit amule.conf

In aMule's configuration file (usually ~/.aMule/amule.conf, or the container's config folder) find the [ExternalConnect] section:

[ExternalConnect]
AcceptExternalConnections=1
ECPort=4712
ECPassword=<MD5 of your password>

• AcceptExternalConnections=1 enables external connections.
• ECPort=4712 is the port (you can change it; remember to enter the same value in the app).
• ECPassword must contain the MD5 hash of the password, not the plain-text password.

Generating the MD5 hash of the password

echo -n "mypassword" | md5sum

Copy the resulting string (32 hexadecimal characters) as the value of ECPassword.

⚠️ Edit the file while amuled is stopped, otherwise your changes will be overwritten on restart.

2. Restart amuled

Restart the daemon (or the container) to apply the changes.

3. Open/forward the port

Make sure the EC port (default 4712/TCP) is reachable from your device:

• Same local network: usually works right away.
• From outside your home: do NOT expose 4712 directly to the Internet. Use a VPN (see below).

Specific case: Unraid / Docker

In aMule containers the configuration lives in a mapped volume (e.g. /config or /home/amule/.aMule). Typical points of attention:

1. Path mapping: check that the app's Incoming and Temp folders are mapped to real Unraid shares, not only to appdata (which usually sits on the SSD cache). You can check the paths as seen by the server in aMule preferences → General → Folders on the server (Mac app).
2. EC port: expose the container's 4712/TCP in the Port mappings.
3. After editing amule.conf, restart the container.

⚠️ Temp folder on the cache

If the temporary files folder points inside appdata (SSD cache), running downloads can fill the cache and prevent files from completing. In that case, with the container stopped, move the .part files to a folder on a large disk and update TempDir accordingly.

Security: use a VPN

The EC protocol is not encrypted: the password is hashed but the command traffic is not. For remote access:

• WireGuard (many routers, including FRITZ!Box, support it natively), or
• Tailscale installed on the NAS/server.

With the VPN active you simply use the server's internal IP in the app. Avoid opening port 4712 to the Internet.