http://test.amule.szerverem.hu/w/api.php?action=feedcontributions&feedformat=atom&user=82.227.132.130AMule Project FAQ - User contributions [en]2026-04-05T22:58:17ZUser contributionsMediaWiki 1.23.3http://test.amule.szerverem.hu/wiki/FAQ_webserverFAQ webserver2008-06-02T19:18:20Z<p>82.227.132.130: </p>
<hr />
<div>== What is [[aMuleWeb]]? ==<br />
Take a look at [[aMuleWeb|this]].<br />
<br />
== How can I setup [[aMuleWeb]] with [[aMule]] v2? ==<br />
To configure it, please follow [[AMuleWeb#Configuring_aMuleWeb|this HowTo]].<br />
<br />
== How can I setup [[aMuleWeb]] with [[aMule]] v1? ==<br />
Read [[Webserver-old|this HowTo]], but be aware that using [[aMule]] v2 is '''recommended''' and that [[aMule]] v1's [[aMuleWeb]] has some security bugs.<br />
<br />
== What should I see when [[aMuleWeb]] is running correctly? ==<br />
After running ''amuleweb'' in a terminal, you should see something like this:<br />
<br />
:''Web Server: Started''<br><br />
:''WSThread: Thread started''<br><br />
:''WSThread: created service''<br><br />
:''WSThread: created socket listening on :4711''<br><br />
:''amuleweb$''<br />
<br />
== Can I run [[aMuleWeb]] as a daemon? ==<br />
Since [[aMule]] 2.0.0-rc6, [[aMuleWeb]] supports ''--quiet'' switch (or ''-q'' also) which renders allows [[aMuleWeb]] to be easily run on the background.<<br />
<br />
However, on previous [[aMule]] releases, although [[aMuleWeb]] works well, it's actually quite tricky to run it in the background because it's continuously asking for user commands and showing the prompt. The obvious way to avoid this would be running amuleweb with the output redirected to ''/dev/null'', but this hogs the CPU due to the constant writing, so a better approach is to use the program [http://directory.fsf.org/GNU/screen.html screen], which is a terminal emulator. In order to run [[aMuleWeb]] inside a virtual terminal, the following command should be executed: ''screen -d -m -S amulewebsession amuleweb -p 7000 -pw password'' (assuming that [[aMule]] is listening for [[External Connections]] on port ''7000'' and the password is ''password''). Then, [[aMuleWeb]] will start listening for HTTP connections, but will show the prompt and all messages in this virtual terminal. It's possible to switch to this terminal using the command ''screen -r amulewebsession'', please refer to [http://directory.fsf.org/GNU/screen.html screen] documentation for info about session switching, internal commands, etc.<br />
<br />
== Why is [[aMuleWeb]] failing to connect? ==<br />
If you followed the [[AMuleWeb|above HowTo]] correctly, make sure that you are using an [[aMuleWeb]] binary distributed with the same release as the [[aMule]] binnary. For example, [[aMuleWeb]] binary from the [[aMule]] 2.0.0-rc3 release will '''not''' connect with [[aMule]] 2.0.0-rc4, [[aMule]] 2.0.0-rc2 or any other version (including v1 versions).<br />
<br />
== Why i always get "''No password specified, login will not be allowed.''" in amuleweb login page with [[aMule]] 2.2 (or CVS), even if i followed correctly how to set passwords, or i already did that successfully in [[aMule]] 2.1.x? ==<br />
Please make sure to follow the [[HowTo_get_aMule_web_interface#Configuration_of_the_aMule_web_interface]], line by line (especially end of article), some behaviors changed in [[aMule]] 2.2.<br />
Make sure to configure amuleweb in monolitic amule or amulegui and before using amuleweb --write-config (unless you know exactly what you are doing).<br />
Verify in the file ~/.aMule/remote.conf if the keys Password and AdminPassword are set with a md5 encrypted password value.<br />
<br />
== Why does the web interface keep going back to the login page ? ==<br />
Try deleting the cookies from the web browser.<br />
<br />
== Version ==<br />
Created by "Unknown User" on 05.07.04 at 00:31<br><br />
Update by Vollstrecker on 22.01.08 at 09:29</div>82.227.132.130