Ошибка could not connect to server

Moderator: Project members

Below you find a step by step guide, if you prefer you can watch our How to Resolve the Critical Error “Could not Connect to Server” video tutorial.

• The user ID and password that you entered. Note that for many website hosting providers, the user ID and password that you use to login to the website itself will be different to the user ID and password that you need for file transfer connections. Look for FTP or SFTP or SSH connection details in the information provided by the hosting provider.
• The type of login configured for this site. In the Site Manager, select the connection
  and check the Logon Type drop down list. Most servers will refuse Anonymous automatically.

Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server" message

If the connection is failing with the status message above, there might be a local network configuration issue. FileZilla/FileZilla Pro has a network configuration wizard that can find common issues in network and router settings.

To diagnose:

1. In the main menu click on Edit > Network configuration wizard….
2. Click on Next
3. Enter details as requested – if you’re unsure, you can usually use the default configuration settings and just click Next at each screen.

Once FileZilla/FileZilla Pro has gathered all the configuration information it needs, it will perform a test connection on a test server run by the FileZilla team. If the test connection works with no errors, then the problem probably exists on the remote site that you’re trying to connect to.

Another possible cause is that the connection is being blocked by a firewall. If you have a local firewall or an antivirus, try to disable it. If that works you may need to add an exception to the firewall configuration to grant FileZilla Pro permanent access to the network.

If you are in a corporate network, you may need to ask the network administrator to open specific FTP ports.
Most FTP servers use port 21, SFTP servers use port 22 and FTPS (implicit mode) use port 990 by default.

The video tutorial below shows how to resolve the critical error “Could not Connect to Server”

Video tutorial: How to Fix Connection Error

Usually, this error occurs when you have incorrect saved certificates in trustedcerts.xml at your local system. To fix this issue, you will need to remove/rename this certificate file from your system.

The file trustedcerts.xml contains certificates for secure websites that you have told your FileZilla client to trust connections to. This file should not be confused with any certificates you have in use if you use FileZilla as a server as well.

In order to remove a saved certificate from Windows System, navigate to %APPDATA%\FileZilla and delete OR rename the trustedcerts.xml file.

In order to remove a saved certificate from Linux System, navigate to ~/.config/filezilla/ and delete or rename trustedcerts.xml file.

Once you remove or rename this file, you will get the prompt to accept the certificate while you attempt to connect to FTP server through FileZilla. On getting the prompt of certificate, select «Always trust this certificate» and then accept it.

Is FileZilla showing Critical error: Could not connect to the server? We can help you fix it.

Usually, FTP clients like FileZilla shows a connection error due to the incorrect protocol or incorrect login credentials.

Here at Bobcares, we often get requests from our customers to fix FileZilla errors as part of our Server Management Services.

Today, let’s see how our  Support Engineers fix this error for our customers.

What is the difference between FTP and SFTP?

Before reading more about the error, let’s get an idea of FTP and SFTP.

The FTP and SFTP are two different protocols used for file transfer.

FTP transfer the password and data in the plain text format whereas, SFTP encrypts the data before sending it to another host.

FTP doesn’t provide a secure channel to transfer files between hosts whereas SFTP offers a secure channel for transferring files between the hosts. Thus, SFTP is found to be more secure than the FTP protocol.

How to fix Critical error could not connect to Server?

At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face this problem.

Now, let’s see how our Support Engineers fix the error for our customer in simple steps.

1. Incorrect Protocol

The customer got the below error when he tried to establish an FTP connection with an SFTP server.

Error: Cannot establish FTP connection to an SFTP server. Please select proper protocol.
Error: Critical error: Could not connect to server

On checking, we found that the protocol is incorrect. For the proper connection, the protocol should be SFTP and not FTP.

We fixed the error easily by enabling the SFTP protocol instead of FTP. Both the SFTP and FTP are different file transfer protocols and the main difference with the protocols is associated with security.

We asked customer to fix the error using these simple steps.

1. Initially, open FileZilla.

2. Then go to File and click the Site Manager option.

3. In the Site Manager, go in the General tab and select SFTP in Protocol.

Finally, choose Logon Type as Normal and provide a valid username and Password.

Also, provide the Host details and Port number as 22.

This fixes the Critical error: could not connect to Server in FileZilla during establishing an FTP connection to an SFTP server.

2. Incorrect login credentials

Very often, some customers may get the below error in FileZilla.

Response: 530 Login authentication failed
Error: Critical error: Could not connect to server

This error occurs when users enter an incorrect username/password or host. So we advise our customers to check the username and password are correct.

[Need any assistance with FileZilla Errors – We can help you fix it]

Conclusion

In short, Critical error: Could not connect to Server in FileZilla happens due to incorrect protocol or wrong login details. Also, we saw how our Support Engineers helped our customer to resolve the connection error in FileZilla.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;