ETIMEDOUT - Connection attempt timed out

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
HenriqueBM
504 Command not implemented
Posts: 9
Joined: 2022-12-07 19:06
First name: Henrique
Last name: Manzke

ETIMEDOUT - Connection attempt timed out

#1 Post by HenriqueBM » 2022-12-20 19:47

So, I've been trying to connect to a FTP server running on linux. At the client I'm getting the following error:

Status: Disconnected from server
Status: Connecting to XXX.XX.XX.XXX:21...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to XXX.XX.XX.XXX:21...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Could not connect to server

Nothing appears at the server side.

I tried opening a certain range of ports on the server side with "sudo ufw allow 11000:12000/tcp" but it didn't help

When trying to connect to a public FTP server I get this error at the client side:

Status: Disconnected from server
Status: Resolving address of speedtest.tele2.net
Status: Connecting to 90.130.70.73:21...
Status: Connection established, waiting for welcome message...
Error: Connection closed by server
Error: Could not connect to server

Connections work the other way though, a client at where this server is at can connect to a server where this client is at.

Sorry to bother you guys so much, I want to finish this before Christmas.

User avatar
botg
Site Admin
Posts: 35508
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: ETIMEDOUT - Connection attempt timed out

#2 Post by botg » 2022-12-21 08:32

Can you connect to the server using https://ftptest.net/ ?

HenriqueBM
504 Command not implemented
Posts: 9
Joined: 2022-12-07 19:06
First name: Henrique
Last name: Manzke

Re: ETIMEDOUT - Connection attempt timed out

#3 Post by HenriqueBM » 2022-12-21 19:43

OBS: To clarify, I will call both computers I am using C1 and C2, currently the problem is that C2 client cant connect to the C1 server.
....

botg wrote:
2022-12-21 08:32
Can you connect to the server using https://ftptest.net/ ?
No. I got "Error: Connection attempt timed out" on both C1 and C2.

I had already tested this and was aiming at at least making it work locally. The connection already works one way like I mentioned (C1 client connects to C2 server).

Also both computers can connect to themselves (C1 client to C1 server/C2 client to C2 server).

User avatar
botg
Site Admin
Posts: 35508
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: ETIMEDOUT - Connection attempt timed out

#4 Post by botg » 2022-12-22 07:58

If ftptest.net cannot work, then the server itself is having problems. Please contact your server administrator or server hosting provider for further assistance.

HenriqueBM
504 Command not implemented
Posts: 9
Joined: 2022-12-07 19:06
First name: Henrique
Last name: Manzke

Re: ETIMEDOUT - Connection attempt timed out

#5 Post by HenriqueBM » 2023-01-26 18:38

botg wrote:
2022-12-22 07:58
If ftptest.net cannot work, then the server itself is having problems. Please contact your server administrator or server hosting provider for further assistance.
What can I try to allow C1 and C2 to connect to each other? the client on C1 can already connect to the server on C2 with no problems. I want to try at first to make it work internally to then build it up from there.

Maybe I didnt disable the firewall the right way?

HenriqueBM
504 Command not implemented
Posts: 9
Joined: 2022-12-07 19:06
First name: Henrique
Last name: Manzke

Re: ETIMEDOUT - Connection attempt timed out

#6 Post by HenriqueBM » 2023-01-31 19:44

Can you at least give me some tips on what to ask them and look out for?

User avatar
botg
Site Admin
Posts: 35508
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: ETIMEDOUT - Connection attempt timed out

#7 Post by botg » 2023-02-01 15:13

Could be anything. From firewalls, to routing issues, to the server not even running.

Post Reply