aMule Forum
English => aMule Help => Topic started by: Ivina on May 22, 2006, 07:20:06 PM
-
Hallo!
Also ich such schon seit Tagen nach einer Problemlösung. Ich hab bei meinem aMule einen HTTP-Proxy eingestellt. Tja nur leider verbindet er mir nicht mit den Servern. Eine Server-Met kann er schon laden..
Die Ports sind auf dem Router freigegeben. Wenn ich den Proxy ausstell, kann ich einwandfrei mit High-ID connecten. Wo liegt das Poblem? An der CVS Version kanns auch nicht liegen. Mit der Stable funktionierts genau analog.
Er gibt mir in der Konsole folgende Meldung aus:
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /root/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /root/.aMule/Incoming/ shared
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
Bitte bitte Hilfe. Ich brauch den Proxy unbedingt..
-
Unfortunately, I can only help in english or portuguese. Most probably your proxy configuration is wrong.
-
I'll translate (into Englisch, cause my Portugues is very, very limited...). Please, wait a sec.
Rough translation:
Hello!
I search for a solution for my problem for some days. I've set a HTTP-Proxy in my aMule. But unfortunatly it doesn't connect to a server. I can download a server.met.
The ports are opened in the router. When I disable the proxy, then I can connect prefectly with an HighID. Where's the problem? It can't be due to the CVS Version. It's the same problem with aMule stable.
That's the output in the terminal:
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /root/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /root/.aMule/Incoming/ shared
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
Please, please help me. I absolutely need the proxy.
-
*lets make it english for phoenix*
well there is still not a lot of information which could help to figure out where the problem is...
-
Hi!
The problem is, I don't get more information. The proxy I use is from an extern server (university). I tested it with a laptop and winxp. It worked fine (but I need to say, I tried eMule instead). What can I do next?
greets
-
well maybe you can write teh sysadmin for your university an email and ask
"cool proxy server you got, what type of software is that"
and maybe he will be nice and tell you if its a squid proxy or any other software....
when you say you used eMule, did you set just "proxy" in the pref, or do you also have to set what type of proxy in eMule ....(http, socks4/5)
-
Hi!
squid/2.5.STABLE12
i set "http" in emule.
lg
Edit: Moved the thread into the English section, should you have any problems just write it in German, there'll be someone to translate it. :)
-
Originally posted by wuischke
I'll translate (into Englisch, cause my Portugues is very, very limited...). Please, wait a sec.
Thanks wuischke! English is fine!
Originally translated by wuischke
Hello!
I search for a solution for my problem for some days. I've set a HTTP-Proxy in my aMule. But unfortunatly it doesn't connect to a server. I can download a server.met.
The ports are opened in the router. When I disable the proxy, then I can connect prefectly with an HighID. Where's the problem? It can't be due to the CVS Version. It's the same problem with aMule stable.
That's the output in the terminal:
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /root/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /root/.aMule/Incoming/ shared
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
Please, please help me. I absolutely need the proxy.
Your terminal output tells me that aMule cannot connect to the server. Check the server address and port in aMule configuration dialog. Pay attention to authentication, if that is the case. Also check if your machine is not configured with a firewall like iptables.
Good luck!
-
Your terminal output tells me that aMule cannot connect to the server. Check the server address and port in aMule configuration dialog. Pay attention to authentication, if that is the case.
2006-05-24 11:47:36: Servers: Trying to connect
2006-05-24 11:47:36: Connecting to DonkeyServer No1 (62.241.53.2 - 62.241.53.2:4242)
2006-05-24 11:47:36: Connected to DonkeyServer No1 (62.241.53.2:4242)
2006-05-24 11:47:36: Lost connection to DonkeyServer No1 (62.241.53.2:4242)
2006-05-24 11:47:36: Connection lost
Also check if your machine is not configured with a firewall like iptables.
iptables accepts all at the moment.
bye
-
Ivina,
Sorry, I said server, but I meant proxy server. Check the proxy server address, port and authentication.
To be sure about iptables, do as root:
#iptables -F
That will flush all your firewall rules. Not very recommended, but usefull for a test.
-
dont you need to reallow all connections after a -F phoenix ?
I think this way, he cant connect nowhere anymore
-
Originally posted by stefanero
dont you need to reallow all connections after a -F phoenix ?
I think this way, he cant connect nowhere anymore
Sorry, I don' t understand what you mean by "reallow all connections". After -F, the tables are flushed, what means that you have no rules in your firewall. So, everything depends on the chains' policies of the "filter" table.
In principle, the starting policy is ACCEPT, but -F does not change a table policy.
I know that Fedora Core X comes with a pre-set of rules in the firewall, and the policy is explicitly set to ACCEPT in the chains of the "filter" and "nat" tables. I don't know about other distros.
So, in FCx, iptables -F should allow all connections.
-
^^thats what I ment
if the default policy "would" be drop then he basically shut himself of ;)
better would be, just to make sure
iptables -F
iptables -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
-
Hi!
Iptables aren't pre-configured on Debian.. that's not the problem.
Check the proxy server address, port and authentication.
Adress and port are ok.
authentication: I have a special ip, which is known by the dns-server.
bye
-
Do this and post the result:
$ telnet xxx.xxx.xxx.xxx yyyy
Where xxx.xxx.xxx.xxx is the ip number of your proxy server and yyyy is the port.
Then, when connected, start typing random characters and until you get a response.
Also try this and post:
$ wget http://xxx.xxx.xxx.xxx:yyyy/
If you get a response, make sure you configure aMule with the same parameters, the ip and the port, do not use a name to be resolved and test with aMule. And please, post the console output of aMule, something similar to this:
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
-
very interesting:
abc:/# ping ***
PING *** (xxx.xxx.x.xxx) 56(84) bytes of data.
--- *** ping statistics ---
43 packets transmitted, 0 received, 100% packet loss, time 41993ms
Do this and post the result:
$ telnet xxx.xxx.xxx.xxx yyyy
abc:/# telnet xxx.xxx.x.xxx:yyyy
telnet: could not resolve xxx.xxx.x.xxx:yyyy/telnet: Name or service not known
???
-
You have to do a telnet xxx.xxx.xxx.xxx yyyy (notice the space!) instead of telnet xxx.xxx.xxx.xxx:yyyy
-
sry..
abc:/# telnet xxx.xxx.x.xxx yyyy
Trying xxx.xxx.x.xxx...
Connected to xxx.xxx.x.xxx.
Escape character is '^]'.after typing 5 minutes i gave it up.. no response
-
Well, how can you be sure that the proxy server you are trying to connect is alive? Ping does not work (100% loss), telnet gives you nothing, ... There are good chances that the server is no longer operating.
-
the proxy is alive. i said it worked with emule.. gaim, mozilla.. ALL WORKS!
aMule not... i removed the router. he isn't the problem too.
-
Ivina,
There is not much I can do to help you. I can test the proxy myself if you want to and if there is no security concern. If that is an option, please send me a private message with the proxy type, address, user and password.
Also, remember I have asked you to post the console output, something like this:
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
-
that won't work. my ip is my authentification.
when i want to connect with the proxy:
Http-CONNECT(0001): 0 -> 1
process_end - ok=false, 0 bytes
hmm. i think i'll must search for another client. :(
-
Verbinde zu DonkeyServer No2 (62.241.53.16 - 62.241.53.16:4242)
Servers: Server 62.241.53.16(62.241.53.16) Port 4242
Proxy: Lost connection event
Verbunden zu DonkeyServer No2 (62.241.53.16:4242)
Servers: Error in serversocket: DonkeyServer No2(62.241.53.16:4242): 4
Verbindung verloren zu DonkeyServer No2 (62.241.53.16:4242)
Verbindung verloren
What means "Error in serversocket: xyz: 4??
-
4 means "Invalid socket (uninitialized)".
-
the proxy works fine with mldonkey.
i think it's a dev-prob of amule. you should fix it or remove the proxy support...
bye
-
You are probably right about beeing a problem with aMule proxy, but in order to fix it, I must be able to reproduce the failure here.
AFAIK, you are the only user reporting this bug. And as proxy works for me here and for lots of other users, I don't see a reason to remove it from the code base.
Good luck with mldonkey. It is a really nice piece of work too.