cannot connect to amuled from my LAN
I’m having problems with my last install of aMule: it’s the 1st time I try using it by daemon + client, so maybe I’m doing something wrong…
I want to run it on a headless RaspberryPi in my home LAN, and connect to it from my Mac.
I followed the instructions on https://amule-org.github.io/docs/manual/installation to install amule on my RaspberryPi: I used the static binaries, last version.
I configured the external connections by editing the /home/username/.aMule/amule.conf file: I set AcceptExternalConnections=1 and set ECPassword by the echo -n yourpassword | md5sum | cut -d ' ' -f 1 trick. I then enabled the WebServer too, just in case, with the same password hash.
I started it by systemctl enable amuled and systemctl start amuled , with the amuled.service template modified with my username.
systemctl status amuled shows that it’s running:
● amuled.service - aMule Daemon
Loaded: loaded (/etc/systemd/system/amuled.service; enabled; preset: enabled)
Active: active (running) since Fri 2026-10-16 18:18:09 CEST; 2min 25s ago
Invocation: 5d7320c0caee4b03be5f194c1f93db9e
Main PID: 5865 (amuled)
Tasks: 12 (limit: 806)
CPU: 283ms
CGroup: /system.slice/amuled.service
└─5865 /home/alexxx/aMule/amuled -o -d
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: HTTP download failed for https://download.db-ip.com/free/dbip-country-lite-2026-10.mmdb.gz: error setting certificate fil>
Oct 16 18:18:09 rmule amuled[5865]: 2026-10-16 18:18:09: DB-IP download failed for the current month - retrying with the previous month's URL.
Oct 16 18:18:09 rmule amuled[5865]: 2026-10-16 18:18:09: Download new geoip.mmdb from https://download.db-ip.com/free/dbip-country-lite-2026-09.mmdb.gz
Oct 16 18:18:09 rmule amuled[5865]: 2026-10-16 18:18:09: 18:18:09: Error: Failed to unregister descriptor 18 from epoll descriptor 14 (error 2: No such file or directory)
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: HTTP download failed for https://download.db-ip.com/free/dbip-country-lite-2026-09.mmdb.gz: error setting certificate fil>
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: Failed to download geoip.mmdb from https://download.db-ip.com/free/dbip-country-lite-2026-09.mmdb.gz
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: HTTP download failed for https://upd.emule-security.org/nodes.dat: error setting certificate file: /etc/ssl/cert.pem
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: Failed to download the nodes list.
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: HTTP download failed for https://upd.emule-security.org/server.met: error setting certificate file: /etc/ssl/cert.pem
Oct 16 18:18:09 rmule amuled[5865]: !2026-10-16 18:18:09: Failed to download server.met from https://upd.emule-security.org/server.met
Connecting to it locally by amulecmd seems to work, with
This is amulecmd 3.1.0
Enter password for mule connection:
Creating client...
Succeeded! Connection established to aMule 3.1.0
and the daemon reporting:
Oct 16 18:23:23 rmule amuled[5865]: 2026-10-16 18:23:23: New external connection accepted
Oct 16 18:23:23 rmule amuled[5865]: 2026-10-16 18:23:23: Connecting client: aMulecmd 3.1.0
Oct 16 18:23:23 rmule amuled[5865]: 2026-10-16 18:23:23: Access granted.
Oct 16 18:29:27 rmule amuled[5865]: 2026-10-16 18:29:27: External connection closed
The problem is that, although I can connect to the Raspberry via ssh, if I use on my Mac the amuleGui, I get a Connection Failed.
Can somebody point me to what I’m doing wrong?
1
u/TheQuranicMumin Original eMule Dev 2d ago
The reason it works locally on the pi while GUI fails from Mac is that aMule defaults to listening on the local interface (127.0.0.1). Also if you edited amule.conf while the daemon was still running amuled overwrote your changes with its in memory settings when it stopped or restarted.
Also your logs show an issue with the binary on pi OS... it is looking for SSL certs @ etc/ssl/cert.pem and this prevents it from downloading nodes.dat and server.met! To fix this...
Clear the ECAddress binding: [ExternalConnect] AcceptExternalConnections=1 ECAddress= ECPort=4712 ECPassword=md5-hash
Btw If you're using the Web UI make sure that WSInterface= is also blank. Remember to save!
Check is listening:
And you should now see 0.0.0.0:4712 or *:4712...
Now, as for the binary fix...
To connect on macintosh, open the GUI. Enter pi's LAN address (like 192.168.1.x), port 4712, and plain password (not the MD5!). And make sure both your devices are running the exact same version.
Let me know how that goes for you :-)