Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dazzathedude]

Hello there,

I have been using emule on the PC for years now and have recently changed to using amule on my MAC G5 running OS X 10.41 which i have found extreemly fast on my 4mb connection and works great much better than on the PC.

however i have been unable to get the remote web access to work.

i have downloaded the binary version 2.0.1 and 2.0.2 enabled amuleweb in the settings/remote controls on port 4711 and have opened/redirected these ports in my firewall. but seem to get no response locally or remotely, and if i try logging in using port 4712 i do get a response (on the server New external connection accepted the followed by Invalid EC Packet received).

please if anyone could advise/help i would GREATLY appeciate it as i would love to use my reliable mac and switch off the pc PERMINANTLY!!!

[ken]

Hi,

The Mac binary we provide is pretty basic, and web server support isn't complete.  Sorry.

See this post for the information necessary to complete it.  Basically, it involves copying the webserver template documents from the source tarball and copying the amuleweb program from inside the aMule.app package (in Contents/MacOS) to your home directory.

I do still intend to improve this.  Some day.  

[dazzathedude]

thanks for the reply, i thought it was me going mad as i have read the forums where people have it working but im glad to know im not. Great program and keep up the fantastic work.

[dazzathedude]

I have check out the link you sent and i have downloaded the latest tarball I have moved the webserver to the hidden .amule folder.
I then manualy run the amuleweb command inside the source of the amule application and have noticed in the log of the amule application window it shows the webserver is running ok.
now when i goto a webbrower type my ip:4711 the webpage comes up looking great but when i type my password it doesn't move on from that same screen and just askes me for the password again, does anyone have an idea??? PLEASE!!!

[ken]

OK, first: are you using the right password?

In the aMule preferences, in Remote Controls, there are several password fields.  The one in the External Connections section is the password that amuleweb uses to gain access to and control over aMule.  In the Webserver section, the one labeled Full Rights is the one that you enter in the web browser to get access to the web server.  For now, leave the Low Rights password blank and uncheck the Enable Low Rights User checkbox.

Second, did you set up ~/.aMule/remote.conf?

When you run amuleweb manually, it uses remote.conf instead of amule.conf for its configuration information, including passwords.  After you set up the passwords in aMule's preferences (which get stored in amule.conf), you can have amuleweb create the remote.conf based off of amule.conf by issuing the command:

amuleweb --create-config-from=~/.aMule/amule.conf

This only has to be done once.  From then on, you can just run amuleweb without any command-line arguments and it will know everything it needs to know.

I hope this helps.  Let me know if you still have problems.  

[dazzathedude]

Hello ken, thanks for you help it is much appreciated and I would would happily pay you or send a donation for your time in helping me.

please bare with me as i maybe doing something stupid but i will explain exactly what i am doing.

1. in the amule program prefs/remote controls i have selected run amule on startup (4711) and in the full rights password i have put lets say i have 1234 as the password and both accept external connections and use tcp port (4712) selected also with 1234 as password.
2. in the user folder/.amule folder i have copied over the whole webserver folder from the latest tarball file (and all the other bits just in case) i have also duplicated the amule.conf and renamed it to remote.conf so there is both a amule and remote.conf file in there
3. i open the source of the amule application and in the contents/MacOS i double click the amuleweb file which opens up a terminal window and asks me to enter a password for the mule connection (I TYPE IN 1234) then it sais creating client
now doing connection
succeeded connection to amule 2.0.2
created socket listening on :4711

and i have noticed now in the amule applications log window it sais
new external connection accepted
connecting client: aMuleweb 2.0.2
Access granted

4. now if i open my browser and type my ip address:4711 i get the amule screen and it asks for my password, i type in 1234 and thats it, it does not go any further just asks for my password again?

i have tried several browsers just in case without any success (also is it ok to use the same password 1234).

PLEASE, PLEASE can you help?

kindest regards

darren

[ken]

You're very welcome.  I'm happy to help.    Since you brought it up, there is a "Make a Donation" button at the top of your screen.    (Not required, of course.  Totally up to you.)

Anyway, I believe this:

i have also duplicated the amule.conf and renamed it to remote.conf so there is both a amule and remote.conf file in there

is your problem.  Although there are some similarities, the formats of amule.conf and remote.conf are different.  It won't work for you to copy amule.conf to remote.conf.

Your best bet at this point is to delete your remote.conf and use the command I suggested above to create an appropriate one.  I'm guessing you're not quite sure how to do that, which is why you didn't earlier.  It's pretty simple:

• Open Terminal (located in Applications -> Utilities)
• Drag the amuleweb icon (the same one you double-clicked in your step 3) into the Terminal window and drop it.  This is just a way to automatically type in the path to that program on the command line.
• Add "--create-config-from=~/.aMule/amule.conf" (without the quotes) to the command line.  You can just copy it from here and paste it in Terminal.
• Press return to execute the command.

If I recall correctly, the command doesn't produce any output.  It just drops you right back at the command prompt after it has done its work.

At this point you can run amuleweb.  If you like, you can double-click it like you're used to doing.  Or, you can just type its path on the command line.  You can use the drag and drop trick (or copy and paste) to type if for you if you like.  Do not include the "--create-config-from" stuff -- just press return after "amuleweb" and it will start running.

Now that all that has been said, there's good news.  I have just completed changes to the code to allow aMule to launch amuleweb automatically as it should.  The next Mac binary (or CVS snapshot for the adventurous types) won't involve any of this hassle.  It'll Just Work(tm).

[dazzathedude]

gee dude you are a guru!!! and thanks for such a speedy responce and I am glad to see there are some great mac developers and support out there.

i did exactly what you have just said now all is working FANTASTIC,

I did try the line you said before but i just got an error pop up (but i didnt drag the amuleweb icon onto the terminal window as i did just now).

I will keep my promise and send you a paypal donation right away.

THANKS ONCE AGAIN

Darren

typical that you have now sorted a working web version of this great program

[Kry]

Donation received Thanks!