OK, that's weird. To figure out what's going on, it might help to see the output from amuleweb. That means running it manually instead of letting aMule run it automatically. So do the following:
(These instructions assume your aMule.app is in /Applications. If it isn't, replace all occurrences of "/Applications/aMule.app" with the proper path to aMule.app.)
- Open the Terminal application (in /Applications/Utilities)
- When you run amuleweb manually, it uses ~/.aMule/remote.conf for its configuration information instead of ~/.aMule/amule.conf. To create this file, do this: /Applications/aMule.app/Contents/MacOS/amuleweb --create-config-from=~/.aMule/amule.conf
You only have to do that once. It will create an appropriate remote.conf, which will be available whenever you run amuleweb manually in the future.
- Kill amuleweb if it's already running: killall amuleweb
- Run amuleweb manually, with verbose output: /Applications/aMule.app/Contents/MacOS/amuleweb --verbose
- Now try to login to amuleweb using your web browser
- Quit amuleweb by giving the "quit" command at the amuleweb prompt
- Copy the amuleweb output from the Terminal window and paste it to a post here.
Hopefully that will help us figure out what's happening.
