amule and web server

[tsolignani]

Hallo everybody.

I installed amule 3.0.0 into my M2 Mac mini.

I went into preferences and enabled both ec and web server.

Ec works, the web server doesn't and I would like to use it to connect to amule from my Android devices. It seems no local web server is running.

Is there something else I can do or configure?

Thank you.

[got3nks]

@tsolignani — welcome. The "Enable Web Server" checkbox in Preferences is read at aMule startup, so toggling it while aMule is running doesn't actually launch amuleweb. The most common cause of "no web server is running" right after ticking the box is just that the GUI needs a full restart.

Steps to get it working:

1. Preferences → Remote Controls → Web Server: make sure both "Enable Web Server" and "Web Server password" are set (the password is mandatory — amuleweb won't accept logins without it). Default port is 4711.
2. Quit aMule completely (⌘Q, not just close the window).
3. Relaunch aMule. On macOS the GUI auto-finds amuleweb inside the .app bundle — you don't need to start it from a terminal. If launch fails for any reason, you'll see an alert dialog.
4. Open http://localhost:4711 on the Mac. You should get the aMule web login. Use the Web Server password you set in step 1.

Once that works locally, for the Android side:

• On the Mac: System Settings → Network → Firewall — allow incoming connections for aMule, or temporarily disable the firewall to test.
• On Android: open http://<Mac's LAN IP>:4711/ (find the IP via System Settings → Network → Wi-Fi → Details). localhost won't work from the phone — that points to the phone itself.

If you've done all that and there's still no web UI:

• In aMule check the log (View → Show server messages, or the bottom-left log pane) for any web server line around startup.
• Run pgrep -fl amuleweb in Terminal — if it returns nothing, the binary isn't running.

Paste what you see in those two and we can take it from there.

[got3nks]

Quick follow-up @tsolignani — coming back to this with a likely culprit. The macOS .app builds shipped to date never bundled the web-template files inside the .app, so even when "Enable Web Server" was set and the GUI auto-launched amuleweb, the binary aborted with FATAL ERROR: Cannot find template: default before it could bind port 4711. The pgrep -fl amuleweb step in my earlier reply was the right diagnostic — if you tried it, you'd have seen no amuleweb running for exactly that reason.

Fixed in #195 (just merged). The first CI build of master after the merge produces a universal macOS .app with the templates bundled correctly.

If you'd like to try it before the next official release: grab the freshly-built universal .dmg from this artifact (44 MB, contains both Intel and Apple-silicon builds). The artifact download requires being signed in to GitHub. Replace /Applications/aMule.app with the contents of the dmg, then in Preferences → Remote Controls → Web Server pick default from the Template dropdown (before the fix it showed "no options available"; after the fix it should list default), set a Web Server password, restart aMule, then visit http://localhost:4711/ — you should now see the login form instead of nothing.

Let me know how it goes.

[tsolignani]

Thank you.

I just tried launching amuleweb from terminal and that's what I got:

mini-cheamore:MacOS tsolignani$ ./amuleweb
FATAL ERROR: Cannot find template: default
This is amuleweb 3.0.0
Enter password for mule connection:

Creating client...
Connection Failed. Unable to connect to 127.0.0.1:4712
mini-cheamore:MacOS tsolignani$

I guess you spot the culprit.

I'll try the download and let you know.

Thank you.

[tsolignani]

I confirm that now it works.

The default template was missing.

Thank you