Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Our experts will login to your server within 30 minutes to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Critical error : Could not connect to Server in FileZilla Solved

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.

Critical error : could not connect to Server in FileZilla

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

Critical error : could not connect to Server in FileZilla

 

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.


PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF