Print

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

[lfroen]

I hate when people gets so stubborn. NO, YOU DIDN'T DO EVERYTHING OR IT WOULD WORK. duh.

Kry, next time before you gonna write user-interfacing application, think AGAIN. Webserver configuration  is not even near to user-friendly.
You right, he didn't do everithing (or it would work), but he can't see it. And IMHO he shouldn't do something else except of clicking on "Enable Webserver" checkbox in preferences.
Imagine:
User: How do I ... ?
Kry: Open terminal and ...
User: What do you mean "terminal" ?

[wuischke]

Well, maybe we should provide a configuration script for those who have no x to improve the usability.
(I mean sth. like a dpkg-reconfigure dialogue)
I graduate atm, but I could try to teach myself some 'advanced' shell scripting when I'm done. I wanted to learn this anyway...

[stefanero]

well lfroen thats basically what you do with normal amule,

open prefs, click enable webserver and set password for external connections, and the webinterface login

how can it be more simple?

with the daemon version of amule, its of course a little more tricky since you dont have a gui

[Kry]

Originally posted by lfroen

I hate when people gets so stubborn. NO, YOU DIDN'T DO EVERYTHING OR IT WOULD WORK. duh.

Kry, next time before you gonna write user-interfacing application, think AGAIN. Webserver configuration  is not even near to user-friendly.
You right, he didn't do everithing (or it would work), but he can't see it. And IMHO he shouldn't do something else except of clicking on "Enable Webserver" checkbox in preferences.
Imagine:
User: How do I ... ?
Kry: Open terminal and ...
User: What do you mean "terminal" ?

Wt, did I code this part of the config? No I didn't. HE can't see it? Wow, what about following the wiki instructions? It WORKS when you do that. Not our fault if he did anything wrong.

I mean, is not that hard. Open amuled. Closed amuled. Edit config. Set EC to 1. Set the EC and webserver password. Set amuleweb to 1 if you want to run it on startup. Close config. Run. Profit.

Want an ncurses configure? Go on. Won't stop you.

Oh, and next time an user says "what do you mean terminal?" when TRYING TO RUN A FUCKING DAEMON, I'll smack him in the head. Heavily.

[Scorpwanna]

I've already explained. I am on debian unstable. I used the apt-get install to install amule-daemon (which also installed the amuleweb). It added to my init.d (run at startup whatever) the amuled and amuleweb. But, when I would run it, amuleweb would not run. When I could eventually get it somehow running, it wouldn't let me login when i gave it the right password. Your wiki may be easy for advanced linux users to understand but i'm not advanced.

your wiki: Run amuleweb -w to generate ~/.aMule/remote.conf and edit it for these options. It previously were on ~/.aMule/amule.conf, but the lines are still on this file, so edit both if in doubt.

The file generated did not contain the same "lines". That sentence doesn't make any since. "It previously were on" throws me off.

amule.conf

[eMule]
AppVersion=aMule 2.1.1
Nick=Sporc
QueueSizePref=50
MaxUpload=0
MaxDownload=0
SlotAllocation=2
Port=4662
UDPPort=4672
UDPDisable=0
Autoconnect=1
MaxSourcesPerFile=300
MaxConnections=500
MaxConnectionsPerFiveSeconds=20
RemoveDeadServer=1
DeadServerRetry=2
ServerKeepAliveTimeout=0
Reconnect=1
Scoresystem=1
Serverlist=0
AddServersFromServer=1
AddServersFromClient=1
SafeServerConnect=0
AutoConnectStaticOnly=0
SmartIdCheck=1
ConnectToKad=1
ConnectToED2K=1
TempDir=/home/brandon/.aMule/Temp
IncomingDir=/home/brandon/.aMule/Incoming
ICH=1
AICHTrust=0
CheckDiskspace=1
MinFreeDiskSpace=1
AddNewFilesPaused=0
PreviewPrio=0
ManualHighPrio=0
FullChunkTransfers=1
StartNextFile=0
StartNextFileSameCat=0
FileBufferSizePref=16
DAPPref=1
UAPPref=1
OSDirectory=/home/brandon/.aMule/
OnlineSignature=0
OnlineSignatureUpdate=5
EnableTrayIcon=0
MinToTray=0
ConfirmExit=0
StartupMinimized=0
3DDepth=10
ToolTipDelay=1
ShowOverhead=0
ShowInfoOnCatTabs=0
ShowRatesOnTitle=0
VerticalToolbar=0
VideoPlayer=
VideoPreviewBackupped=1
StatGraphsInterval=3
statsInterval=30
DownloadCapacity=3
UploadCapacity=3
StatsAverageMinutes=5
VariousStatisticsMaxValue=100
SeeShare=2
FilterLanIPs=1
IPFilterAutoLoad=1
IPFilterURL=
FilterLevel=127
FilterMessages=0
FilterAllMessages=0
MessagesFromFriendsOnly=0
MessageFromValidSourcesOnly=1
FilterWordMessages=0
MessageFilter=
ShareHiddenFiles=0
AutoSortDownloads=0
NewVersionCheck=0
ExecOnCompletion=0
ExecOnCompletionCommand=sh -c '~/example.sh "%FILE" %HASH'
Language=
SplitterbarPosition=75
YourHostname=
DateTimeFormat=%A, %x, %X
IndicateRatings=1
AllcatType=0
ShowAllNotCats=0
DisableKnownClientList=0
DisableQueueList=0
MaxMessageSessions=50
PermissionsFiles=416
PermissionsDirs=488
Address=
[FakeCheck]
Browser=0
BrowserTab=1
CustomBrowser=
[Proxy]
ProxyEnableProxy=0
ProxyType=0
ProxyName=
ProxyPort=1080
ProxyEnablePassword=0
ProxyUser=
ProxyPassword=
[WebServer]
Enabled=1
Password=098f6bcd4621d373cade4e832627b4f6
PasswordLow=
Port=4711
UseGzip=1
UseLowRightsUser=0
PageRefreshTime=120
Template=
[ExternalConnect]
AcceptExternalConnections=1
ECUseTCPPort=1
ECAddress=
ECPort=4712
ECPassword=098f6bcd4621d373cade4e832627b4f6
ShowProgressBar=1
ShowPercent=0
UseSrcSeeds=0
UseSecIdent=1
IpFilterOn=1
[Razor_Preferences]
FastED2KLinksHandler=1
FullQueueSources=0
HighQueueRankingSources=0
HighQueueRanking=1200
AutoDropTimer=240
NoNeededSourcesHandling=2
[SkinGUIOptions]
UseSkinFile=0
SkinFile=
[Statistics]
MaxClientVersions=0
TotalDownloadedBytes=0
TotalUploadedBytes=0


remote.conf
(note: i have changed the Host= line to all sorts of addresses)

Locale=
[EC]
Host=localhost
Port=4712
Password=098F6BCD4621D373CADE4E832627B4F6
[Webserver]
Port=-1
Template=php-default
UseGzip=0
AllowGuest=0
AdminPassword=098F6BCD4621D373CADE4E832627B4F6
GuestPassword=

sporc:/# ls -la /usr/bin/amule*
-rwxr-xr-x 1 root root 1721136 2006-04-19 03:44 /usr/bin/amuled
-rwxr-xr-x 1 root root  488716 2006-04-19 03:44 /usr/bin/amuleweb
sporc:/#

sporc:/# ls -la /usr/local/bin/amule*
ls: /usr/local/bin/amule*: No such file or directory
sporc:/#

--------

The debian internal ip is: 192.168.1.45.

After running the init.d for starting the daemon process I would try to go to 192.168.1.45:4711 and recieve connection refused.

In my debian bash shell "command prompt" i'd type:


sporc:/# amuleweb -h localhost
This is amuleweb 2.1.1

Creating client...
Connection Failed. Unable to connect to the specified host

but typing this works for getting the amuleweb running:

sporc:/# amuleweb -h 192.168.1.45
This is amuleweb 2.1.1

Creating client...
Succeeded! Connection established to aMule 2.1.1

--------------------------------------
|          aMule Web Server          |
--------------------------------------

Use 'Help' for command list

Web Server: Started

WSThread: Thread started
aMuleweb$ WSThread: created socket listening on :4711

I'm using the password test for everything until it gets working, before when I would run this, i'd put in test and it would just refresh the page back to the login. I managed to login now running as root. I am able to get to the web interface using the ip address. Yet when I try to run it under my normal linux account the login page still refreshes and is not logging in. I check and see this:

Web Server: Started
aMuleweb$
WSThread: Thread started
WSThread: created socket listening on :4711
Processing request [original]:
No session opened - will request login
Session created - requesting login
Checking password
Password bad
Processing request [redirected]: login.html

Again I have set every password to "test".

I want to login to this from a home PC the debian computer has my webserver on it called scorpwanna.com I tryed scorpwanna.com:4712 (external connection) and it didn't work.

[Scorpwanna]

ok, I'm now able to login using the password test at the following location 192.168.1.45:4711

I removed my config for remote.conf (apparently it was created when I was logged in as root) recreated it under my normal user account. restarted the amule-daemon I can login.

But I'm still needing to run amuleweb manually and stay logged into my shell so that it still runs.

When i apt-get install amule-daemon it created this file:

/etc/init.d/amule-daemon

#! /bin/sh


PATH=/bin:/usr/bin:/usr/local/bin/:/sbin/:/usr/sbin/
DAEMON=/usr/bin/amuled
WEBDAEMON=/usr/bin/amuleweb

if [ -f /etc/default/amule-daemon ]; then
        . /etc/default/amule-daemon
fi

if [ -z "$RUN_AT_STARTUP" -o "$RUN_AT_STARTUP" != "YES" ]; then
        echo "aMule daemon not starting, edit /etc/default/amule-daemon for start it"
        exit 0
fi


HOME=`getent passwd $AMULED_USER | awk -F: '{print $6}'`

if [ -z "$HOME" ]; then
        echo "aMule user does not exists or has no home folder. Check /etc/default/amule-daemon settings"
        exit 0
fi

start ()
{
    echo -n "Starting aMule : amuled"
    export HOME
    start-stop-daemon --chuid $AMULED_USER --user $AMULED_USER --start --exec $DAEMON --background
    echo "."
}

stop ()
{
    echo -n "Stopping aMuleWeb : amuleweb"
    export HOME
    start-stop-daemon --stop --retry 5 --oknodo --quiet --chuid $AMULED_USER --user $AMULED_USER --exec $DAEMON
    start-stop-daemon --stop --retry 5 --oknodo --quiet --chuid $AMULED_USER --user $AMULED_USER --exec $WEBDAEMON
    echo "."
}


case "$1" in
  start)
        start
    ;;
  stop)
        stop
    ;;
  reload)
          stop
          start
    ;;
  force-reload|restart)
        stop
        start
        ;;
  *)
    echo "Usage: /etc/init.d/amule-daemon {start|stop|restart|force-reload|reload}"
    exit 1
    ;;
esac

exit 0

-------------------------

Though it has an echo line saying it stops the amuleweb it doesn't appear to have a starting for it. I think maybe I need to add it. But to where? Localhost? 192.168.1.45? I want to access this from another PC location targeting scorpwanna.com.

[stefanero]

as I said before -> post your amule.conf file plz,

if everything is correct there, you shoudl NOT need to run amuleweb separte,

but looks like you did nto read my post....

[Scorpwanna]

perhaps you are the one that can't read, i posted it already in this thread.

Just because steps taken to get to a certain point, gets one person there, doesn't mean those same steps will lead a person in the same direction.

It's been my experience that every computer system is different. Different things need to be set just so something else can work. I am not using a simple point and click gui. I'm using terminal/bash shell command prompt whatever you wanna call it to set this up. And I followed your instructions on your wiki with null results. Under my root access to my debian I apt-get installed. The amule.conf file was created under my normal user name but the remote.conf was created under root. Which apparently wasn't allowing me to access it as a normal user, possibly due to file permissions. But I found out quick that i needed to be logged in under my normal user account to create the remote.conf file. Something your wiki didn't mention on the amuleweb page. Then there's the port forwarding that each router/modem has that is different. You didn't mention forwarding of ports if a pc is connected to a network to the 4711-4712.

The only problem now is actually finding out why amuleweb isn't running when the daemon is started. The amule-daemon which was automaticly placed in the etc/init.d/ may stop the process, but it never starts it. Which is why ive had to manually start it and use an internal machine ip address to even access it over my network.

The Host= line of the config, it's default at localhost. Do I need to change this? Because again, just typing "amuleweb" (at my terminal bash shebang line) and then the password gives me a host error. It's only if i type out the internal ip after that it even gets connected.

[stefanero]

well you said you changed some things, so I figured it was not up2date anymore...

ok try one thing plz

telnet localhost 4712

in a normal terminal, lookt to me you cannot lookup localhost, since you had to use -h IP_ADDRESS

if this does NOT work add a line like this to your /etc/hosts file

127.0.0.1       localhost localhost.localhost

then retry the telnet command, if it works restart the whole amule(d) thingy, and again you do NOT need to start amuleweb seperate!! you have in your amule.conf file

[WebServer]
Enabled=1

^^ the 1 lets it start automatically, you can check if its running with

ps ax | grep amuleweb

[Scorpwanna]

Actually the amule.conf file has not been changed nore has the remote.conf.

brandon@sporc:~$ telnet localhost 4712
telnet: could not resolve localhost/4712: Name or service not known
brandon@sporc:~$

/etc/hosts file
-------------------------

127.0.0.1       scorpwanna.com          scorpwanna.com  sporc
#127.0.0.1      localhost.localdomain   localhost       debian
192.168.1.45    scorpwanna.com          scorpwanna.com  sporc
-------------------------

brandon@sporc:~$ telnet scorpwanna.com 4712
Trying 127.0.0.1...
Connected to scorpwanna.com.
Escape character is '^]'.

--------------------------

I then uncomment the other 127 line and try the telnet again:

sporc:/home/brandon# telnet localhost 4712
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.

I have the line commented because of my server, webserver and samba filesharing.

brandon@sporc:~$ ps ax | grep amuleweb
19812 pts/0    S+     0:00 grep amuleweb
brandon@sporc:~$


Hope this info helps. And thanks for putting up with me.

[stefanero]

sporc:/home/brandon# telnet localhost 4712
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.

^^ if it like that its OK,

you can have one or more names for 127.0.0.1 so having both in there is just fine...also for webserver, samba and so on....

so remove the comment, restart amule(d) and see if it works

btw: it would be really better if you first try without teh init.d script, when you have everything running, and it works correct use the init.d script you never know if there is some error in there aswell...

so run on the console (with the amule user)

amuled -f

then do

ps ax | grep amule

you should see at least one amuled process and one amuleweb...
with

netstat -ntpl | grep amule

you can check which tcp-ports are used by mule, you should have 2 amuled (4612 and the normal 4662) and one for amuleweb(if its running) 4711

[Scorpwanna]

if i leave it uncommented and restart the amule(d) thing i am able to access (without running a separate process of amuleweb)  using in my browser http://192.168.1.45:4711 (from another PC on my network). So that is solved. Thanks.

Now for the remote (from another PC not on the network).

I just tryed http://scorpwanna.com:4711 from this PC i'm on now and it said connection refused again, (i'm vncing) so i tryed it in my browser (on the network) again, and it said the same. I had to restart the amule(d) again and both locations are working right now. So it is functioning.

Thanks. Sorry for the fuss and dogging your wiki. It was helpful to a point but there was more to this than just simple settings.

[stefanero]

ah cool its working  

[Scorpwanna]

yeah as long as i dont try port 4712 it will stay running, if I try that port it seems to crash it and i have to restart the daemon. So I suppose I'll just not have that port forwarded and just use 4711 for all of it. Thanks again.

[stefanero]

well port 4712 is just remote-apps like -> amulecmd, amuleweb or amule-remote-gui

so you should not point the webbrowser to it, 4711 is for the webbrowser...