Is there another default port?
- Thread starter fitnheal
- Start date
- Status
- Messages
- 3,819
- Reaction score
- 163
- Points
- 63
https://wiki.filezilla-project.org/Network_Configuration...please see troubleshooting. Yes sir, that is the wiki page I went to first for the x10hosting. Then I found the link I posted when I got errors trying to log into the FTP.
Response: 530 Login authentication failed
Error: Critical error
Error: Could not connect to server
Troubleshooting
The following are a few troubleshooting suggestions:
Unfortunately, many personal firewalls and consumer routers are flawed or in some cases, even actively sabotage FTP (e.g. SMC Barricade V1.2). First of all, as with all software, you should keep everything updated. This includes the firewall software as well as the firmware version of your router.
If that does not help, you might want to try to uninstall your firewall to see what happens. Simply disabling your firewall might not work, as some firewalls cannot be fully disabled.
If possible, try to connect directly to the internet without a router.
If you are trying to setup a server and it works fine within your LAN but is not reachable from the outside, try changing the listening port. Some ISPs don't like their customers to host servers and they may block ports with numbers under 1024.
Another issue may occur if you are hosting an FTP server on default port 21. There might be a firewall at the ISP side of your connection which can do odd things like changing the port for PASV commands. Try using another non-default port for your FTP server.
If you encounter "cannot open data connection" on a random basis (i.e., the ftp client can connect to the ftp server without problem for many connections until it encounters this problem), one possible reason may be that your client PC anti-virus software is configured to block outgoing connections on certain ranges of ports. When your ftp connections are running in pasv mode, the client-side outgoing ports are selected randomly and some of those randomly selected ports may be blocked by the anti-virus software. To identify this problem, read your anti-virus log on the client. In general, any software that can block certain ranges of outgoing ports (such as PC firewalls) can cause similar FTP grief.
Response: 530 Login authentication failed
Error: Critical error
Error: Could not connect to server
Troubleshooting
The following are a few troubleshooting suggestions:
Unfortunately, many personal firewalls and consumer routers are flawed or in some cases, even actively sabotage FTP (e.g. SMC Barricade V1.2). First of all, as with all software, you should keep everything updated. This includes the firewall software as well as the firmware version of your router.
If that does not help, you might want to try to uninstall your firewall to see what happens. Simply disabling your firewall might not work, as some firewalls cannot be fully disabled.
If possible, try to connect directly to the internet without a router.
If you are trying to setup a server and it works fine within your LAN but is not reachable from the outside, try changing the listening port. Some ISPs don't like their customers to host servers and they may block ports with numbers under 1024.
Another issue may occur if you are hosting an FTP server on default port 21. There might be a firewall at the ISP side of your connection which can do odd things like changing the port for PASV commands. Try using another non-default port for your FTP server.
If you encounter "cannot open data connection" on a random basis (i.e., the ftp client can connect to the ftp server without problem for many connections until it encounters this problem), one possible reason may be that your client PC anti-virus software is configured to block outgoing connections on certain ranges of ports. When your ftp connections are running in pasv mode, the client-side outgoing ports are selected randomly and some of those randomly selected ports may be blocked by the anti-virus software. To identify this problem, read your anti-virus log on the client. In general, any software that can block certain ranges of outgoing ports (such as PC firewalls) can cause similar FTP grief.
For a host I've tried both fitnhealthyfamily.x10.mx and vox.x10hosting.com/home/fitnheal
Username I've used it the one I log into with x10hosting, same for the password.
As far as I know I'm using regular FTP. It's the quick connect at the top of FileZilla.
I've also allowed the program into my firewall, thinking that may be the issue.
Nothing resolved it so far.
Username I've used it the one I log into with x10hosting, same for the password.
As far as I know I'm using regular FTP. It's the quick connect at the top of FileZilla.
I've also allowed the program into my firewall, thinking that may be the issue.
Nothing resolved it so far.
I had to use port 22...here is the link to the information I found.
https://wiki.filezilla-project.org/Using
Nope it timed out...that wasn't it either
https://wiki.filezilla-project.org/Using
Nope it timed out...that wasn't it either
Attachments
- Status