Binding on port 22

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

Moderator: Project members

Post Reply
Message
Author
linkjoy123
500 Command not understood
Posts: 4
Joined: 2022-11-14 19:37
First name: Vinny
Last name: C

Binding on port 22

#1 Post by linkjoy123 » 2023-02-06 16:44

Can FileZilla server be bound to port 22 as well? The Port is allowed in our Firewall to the FTP server, but people who are using port 22 can not connect. Does it not work with the latest version of FileZilla server (1.6.6)? I tried putting the binding of port 22 on the 0.0.0.0 inbound, or even the IP we are using for it, and it does not work.

Does FileZilla not support this anymore?

CrimpOn
226 Transfer OK
Posts: 104
Joined: 2021-10-01 18:25
First name: D
Last name: B

Re: Binding on port 22

#2 Post by CrimpOn » 2023-02-06 17:54

I do not see any reason why FileZilla could not be assigned to as many ports as you want, including port 22:
Just add more lines to the configuration table:
port22.JPG
port22.JPG (32.86 KiB) Viewed 4015 times
This may confuse people because port 22 is typically used for SMS connections.

User avatar
boco
Contributor
Posts: 26914
Joined: 2006-05-01 03:28
Location: Germany

Re: Binding on port 22

#3 Post by boco » 2023-02-06 21:17

Wrong, port 22 is reserved for SSH/SFTP. The regular FileZilla Server does not support SFTP, only the Pro Enterprise Server does.

Users cannot connect because their clients make false assumptions, attempting SFTP connections on port 22 where you want to serve FTP. So, it can be bound to 22, but the result is total chaos.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org

CrimpOn
226 Transfer OK
Posts: 104
Joined: 2021-10-01 18:25
First name: D
Last name: B

Re: Binding on port 22

#4 Post by CrimpOn » 2023-02-06 23:19

Really sorry about the typo, (SMS instead of SSH. SMS refers to cell phone text messages.)

What I intended to point out that FileZilla could be configured to listen on any ports, just as web servers were often configured to listen on port 8080 instead of port 80.
The obvious downside to doing this is that users attempting to connect could be confused. Telnet could listen on port 21 rather than port 23 and would be happy to do so. Users would be totally confused.

Long (long) ago we used to test web sites by having telnet connect to port 80. Tested SMTP by telnetting to port 25, etc.

"Chaos" indeed.

User avatar
boco
Contributor
Posts: 26914
Joined: 2006-05-01 03:28
Location: Germany

Re: Binding on port 22

#5 Post by boco » 2023-02-07 02:19

What I intended to point out that FileZilla could be configured to listen on any ports, just as web servers were often configured to listen on port 8080 instead of port 80.
Yes, but 8080 is just an alternative port to 80, also meant for HTTP, often used by web proxies. Using a port reserved for a different service is another can o' worms.
The obvious downside to doing this is that users attempting to connect could be confused. Telnet could listen on port 21 rather than port 23 and would be happy to do so. Users would be totally confused.
Sure, but these ports are reserved for a reason. Not only users would be confused, but it totally sets up clients, as clients usually know about the default ports for services they support. For example, just specifying a hostname and entering 22 as port in FileZilla will always attempt to connect using SFTP. An FTP server on that port will not understand the client and vice versa, they speak different languages (read: protocols). Using protocol overrides in FileZilla will get you connected fine, but you still get a warning that the selected port is usually in use by a different service.
Long (long) ago we used to test web sites by having telnet connect to port 80. Tested SMTP by telnetting to port 25, etc.
Yes, did that, too. However, you can't compare that. Telnet is kind of a very basic TCP protocol and many later protocols base on it. Thus, it can be used to "ping" compatible services for a heartbeat, success means the service is live. Basically the advanced version of the ping command, which only detects servers, not services.


Another fact why using 22 is pointless. FTP will still needs its data port range allowed and forwarded to function. While the real SFTP protocol doesn't need data ports, setting FTP to 22 won't make its requirements magically disappear. So, if you still have to care for the data port range, just so it right and use the FTP port 21 (or a totally custom one above the first 1024 reserved ports). Custom ports have to be specified in clients, true for all protocols.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org

Post Reply