Moderator: Project members
-
NuShen
- 500 Command not understood
- Posts: 4
- Joined: 2008-05-01 19:07
- First name: Ashley
- Last name: Cain
Error, could not connect to server
#1
Post
by NuShen » 2008-05-01 19:23
I set up FZ Server and it ran very nicely. I rebooted my computer and it’s giving me this error over and over…
_____________________________
Reconnecting to server…
Error, could not connect to server
Trying to reconnect in 5 seconds
_____________________________
I use a D-LINK router with a Verizon DSL (Dynamic) connection.
Windows XP Professional
Norton Internet Security
FZ Server is setup to connect using IP 127.0.0.1:14147
Port forwarding on the router comes in two categories;
— Port Forwarding, allowing a network PC to be selected/entered (i.e. 192.168.0.100) and a Start port and End port and then selection of TCP/UDP/Any
— Application Rules, allowing a Trigger Port and seperate Firewall entry with TCP/UDP/Any selection as well
I went through the FAQ and the link in your sig and didn’t see anything relating and also parused the forums. So if you would please, run me through the settings you recommend and any troubleshooting suggestions? Hopefully I can get this up and running by my deadline tonight!
-
boco
- Contributor
- Posts: 26451
- Joined: 2006-05-01 03:28
- Location: Germany
Re: Error, could not connect to server
#2
Post
by boco » 2008-05-01 19:40
Check if the FZ Server service runs. If it does, I’d suspect Norton (yuck).
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
NuShen
- 500 Command not understood
- Posts: 4
- Joined: 2008-05-01 19:07
- First name: Ashley
- Last name: Cain
Re: Error, could not connect to server
#3
Post
by NuShen » 2008-05-01 19:59
Hrmph…
I have FileZilla Server Interface.exe running, nothing with just «Server» so I’m assuming that leads us to Norton? If that’s the case, I already have it set to «Allow», meaning it lets FZ do whatever it wants to but apparently there’s some super secret process going on to conspire against FZ.
So how do we go about twisting Norton’s arm and blindfolding it in one eye to ignore FZ? Also, could you run me through how you want those router settings set just to be sure I didn’t do something silly? It’s very possible I flaked and did, in fact, do something very silly in my router settings out of panic and deadline evilness.
-
boco
- Contributor
- Posts: 26451
- Joined: 2006-05-01 03:28
- Location: Germany
Re: Error, could not connect to server
#4
Post
by boco » 2008-05-01 22:52
Look at the picture. These two components have to be running for successfully operating the server.
1. Press WINDOWS+R (or click Start-Run…)
2. Enter «services.msc» (without the quotes)
3. Search for the Filezilla FTP Server service
4. Check if it’s running
Post the results here.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
NuShen
- 500 Command not understood
- Posts: 4
- Joined: 2008-05-01 19:07
- First name: Ashley
- Last name: Cain
Re: Error, could not connect to server
#5
Post
by NuShen » 2008-05-01 23:20
Okay, I found one called «FileZilla Server FTP server» and noticed it was set to «Manual» service type. I click «Start» and vwa la… it was working again. I still need to test if it can be accessed from the outside, but I’m confident it will work.
Thank you!!
-
boco
- Contributor
- Posts: 26451
- Joined: 2006-05-01 03:28
- Location: Germany
Re: Error, could not connect to server
#6
Post
by boco » 2008-05-02 06:59
Set the service to ‘Auto’ so it starts up every time the OS is booted.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###
-
NuShen
- 500 Command not understood
- Posts: 4
- Joined: 2008-05-01 19:07
- First name: Ashley
- Last name: Cain
Re: Error, could not connect to server
#7
Post
by NuShen » 2008-05-02 10:15
Alright. It’s now set to auto and seems to be acting normal. Again, thank you so much!
-
coconutdog
- 500 Command not understood
- Posts: 5
- Joined: 2010-11-21 00:53
- First name: Matt
- Last name: Wilson
Re: Error, could not connect to server
#8
Post
by coconutdog » 2015-09-02 07:52
Try entering 127.0.0.1 as the server address.
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.
This error usually means that the login details or method set for a remote connection are incorrect.
Check:
- 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:
- In the main menu click on Edit > Network configuration wizard….
- Click on Next
- 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
Before we get into the solution to the «Cannot connect to server» problem. Let’s look at some of the underlying causes of this scenario.
To begin, you must understand that when you use the internet, you are a part of a Client and Server Network. You, as a client, request the resource, and the server responds with the requested result.
Let’s say you want to open a web app or a website. This request is routed to the backend web server via a router and an ISP, and the server responds with all of the content you requested.
When there is a connectivity issue between the client and the server, you may receive an error message such as «Cannot connect to Server.»Actually, this appears to be a generic error message, and there could be many causes of the problem which makes troubleshooting difficult because you may need to know your computer, network card, local network, router, ISP, and the entire internet, status code, web server issue, client to server connections, server software, firewall, and many more. There is no such thing as a one-to-one problem and a solution to a problem. You must have a strong technical background in order to identify and solve the problem.
This error is similar to the generic error: Unable to Start Laptop. There could be several reasons for this, and determining the root cause of the problem can be difficult, necessitating the assistance of an IT expert. The same thing happens when the error message «Cannot connect to server» is displayed. We don’t know what’s causing the problem here. So let’s take a look at the various causes of them which might help you to solve the problem.
Table of Contents
- 1 Client Firewall Blocking
- 2 Malware and Virus in your Computer and Server
- 3 Antivirus programs, anti-spyware programs
- 4 Router Firewall Blocking
- 5 Check third-party firewall
- 6Connection Problems between Your Router and ISP
- 7 Client Cache
- 8 Server Configuration and Fault // Main Cause of the Problem
- 9 High Load to Server
- 10 DNS servers misconfigured
- 11 Software Issue
- 12 Games File Issue
- 13 Incorrect Database and Website/Software Login Credential
This issue applies to any website, app, game, mobile (android, ios), or browser (safari, chrome, etc)So, let’s look at the hit and trial method of the cause and solutions to it.
1 Client Firewall Blocking
Your computer firewall may prevent you from accessing a specific website in order to get the required results, and you may receive the error message «Cannot Connect to Server.»
Solution 1: You can try disabling all firewalls at once and attempting to access the same website. You might be able to access the site if you’re lucky.
Here are steps for disabling the firewall in Windows OS
- Goto Run and type: firewall.cpl
- Click on Turn Windows Defender Firewall On or Off
-
Check the following two radio buttons:
Under Private network settings: Turn off Windows Defender Firewall (not recommended)Under Public network settings: Turn off Windows Defender Firewall( not recommended)
- Next, try connecting to the website.
Note: You have to turn on your defender firewall to protect your computer.
Solution 2: You can try another website, and if you are able to access another site, it is possible that the web server, routers, or ISP is blocking that particular site.
2 Malware and Virus in your Computer and Server
Sometimes malware and Virus may block to access the website.
Solution: You can try performing scanning on your computer against viruses and malware.
3 Antivirus programs, anti-spyware programs
Sometimes antivirus programs and anti-spyware programs might be blocking connections to the Internet.
Solution: Simply try disabling antivirus programs and anti-spyware programs and try again.
4 Router Firewall Blocking
It’s possible that your modem or router has its own firewall. They may prevent access to the remote web server.
5 Check third-party firewall
If you are running any third-party firewall applications such as Anti NetCut3, Tinywall, ZoneAlarm Free Firewall 2017, PeerBlock or any other, then simply check the settings on those applications as well and make sure Games and Application is allowed through those programs, or disable the firewall program and check again to see if the issue with connectivity has been resolved.
6Connection Problems between Your Router and ISP
There could be a problem with connectivity between your router and ISP. You send the request, it reaches the router, and the router sends it, but your ISP blocks it, or something similar happens.
From your side, just restart your router. To restart your router, all you need to do is disconnect it from power for 30 seconds. After that, reconnect it to its power source and wait one minute for it to finish starting up. This resolves a significant number of connectivity problems.
Also, you can seek help from ISP for identifying the problem.
Also, you can try connecting to another network(if available).
7 Client Cache
The cache cannot be the source of these problems, but clearing the browser cache and cookies can sometimes resolve the issue.
In google chrome, you can apply the following steps to clear caches and cookies.
1 Launch Chrome on your computer.
2 Click 3 horizontal dots in the upper right corner.
3 Click More tools, followed by Clear browsing data.
4 Select All time if you want to delete everything.
5 Check the boxes next to «Cookies and other site data» and «Cached images and files.«
6 Click the Clear data button.
7 Now it’s better to restart your browser.
8 Server Configuration and Fault // Main Cause of the Problem
The server configuration is the root cause of these errors. Server A firewall may be preventing access to the website.There could be a disk failure, a RAM failure, a software problem, and so on in the server.
You might have server errors like:
- Internal Server Error 500
- Not Implemented 501
- Bad Gateway 502
- Gateway Timeout 503
- HTTP Version Not Supported 504
- Variant Also Negotiates 505
- Insufficient Storage 507
- Loop Detected 508
- Not Extended 509
- Network Authentication Required 511
These are general issues, and if a client starts receiving these errors, they may become frustrated, so you simply receive Internal Server Error or an «Unable to connect to server» error.
9 High Load to Server
When there is a high load on the server then you might get an «Unable to connect to server» generic error.
Solution: You cannot do anything. Simply try connecting to the server later.
10 DNS servers misconfigured
Sometimes misconfigured DNS server can cause the problem.
The solution you can try is: Set up the right DNS server.
You can get Preferred DNS Server, to the number 8.8.4.4 and the Alternative DNS server to 8.8.8.8. These are Google Public DNS IP Addresses.
DNS stands for domain name system, and it is used to load web pages on the internet. When dealing with bad DNS, Google DNS returns accurate results. It also appears to be faster than the default DNS, which speeds up browsing. Google Public DNS is fast, dependable, and performs well.
11 Software Issue
Some software may have an issue with it, and when it requests a resource from the server, due to a software error, it simply displays «Unable to connect to server » with no reason or explanation.
Solution: If you are using popular software then it will get fixed soon in the next update.
If you are using WordPress and get «Unable to connect to server» without any reason then try reinstalling WordPress Core. Also, check Your Plugins and Themes in WordPress which might cause this problem.
In the case of games and software that required a login, simply log out and log back in, this might fixed the issue.
12 Games File Issue
Some of the game’s files may be corrupted and you may get unable to connect to the server issue because you are not able to connect to the server due to a file issue.
Solution: Try repairing the files and if possible try to download error games dependent files from the game’s official site.
13 Incorrect Database and Website/Software Login Credential
If your website provides a login page and you have to enter login credentials and when you mistyped username and login then you might get the «Username and password» incorrect or a generic error like «Cannot connect to server»
If you are using a database and you have used an incorrect userId and password then you might get a Cannot connect to a server error.
Solution: Try providing current credentials to log in.
FAQ:
Lost Ark Games Could Not Connect To Game error
Ans: If possible apply above mention fixes, if it does not then you can try the below ways to fix it.
- Reboot your steaming and the game.
- Repair Lost Ark Steam game files
Reboot your steaming and the game. Repair Lost Ark Steam game files Check the following radio button: Under Private network settings: #1 Turn off Windows Defender Firewall (not recommended) Under Public network settings: #2 Turn off Windows Defender Firewall( not recommended)
При подключении через FTP клиент Filezilla один за другим пишутся сообщения в верхней части окна. Это логи FTP подключения. Для человека, незнакомого с протоколом FTP, эти сообщения будут непонятными. Но в случае сбоя именно они помогут найти причину ошибки. Если вы столкнулись с такими ошибками, не спешите писать в техподдержку. Есть частые ошибки, которые легко решаются самостоятельно.
Ошибка Too many connections
Означает что к вашему FTP аккаунту выполнено много подключений. Не волнуйтесь, вряд ли кто-то кроме вас сейчас подключен к аккаунту. В подавляющем большинстве случаев проблема возникает из-за устаревших сессий, которые не были своевременно закрыты.
Перейдите в CPanel, раздел Подключения FTP. Удалите все открытые сессии. После этого откройте настройки Filezilla (Редактирование — Настройки — Передачи — Число одновременных передач — установите 2). Также установите пассивный режим подключения (Редактирование — Настройки — Соединение — FTP — Режим передачи — Пассивный). Отключитесь и подключитесь по FTP заново.
Ошибка Connection attempt failed with eai_noname
Проверьте хост, указанный в настройках подключения. Вы могли ошибиться при его вводе, или же он может быть недоступным из сети. Также вы можете подключаться к старому, уже несуществующему серверу (аккаунты переносятся между серверами в целях балансировки нагрузки). В общем случае в качестве хоста для подключения можно использовать адрес сайта без http:// и www.
Ошибка Command: AUTH TLS. Error: Could not connect to server
Сбой при подключении через зашифрованный канал. Причин может быть достаточно много, например если на сайте не установлен SSL сертификат, или сертификат не принимается этой версией Filezilla. Универсальное решение — отключить TLS. В настройках подключения Filezilla под выбором протокола есть выбор шифрования, поставьте Only use Plain FTP.
Ошибка 30 Login authentication failed
Сверьте логин и пароль, скорее всего они неправильные. Попробуйте набрать их вручную, а не скопировать в поля, чтобы исключить копирование лишних пробелов и невидимых символов. Основной FTP логин указывается без символа @ и имени домена. Дополнительные — с этим символом и именем домена (например ftpuser@test.com). Если уверены что все верно — попробуйте сбросить пароль для аккаунта с которого вы пытаетесь подключиться. Проверьте также хост, такая ошибка возможна если вы подключаетесь к неправильному серверу. Если ничего из этого не помогло — напишите в техподдержку и мы постараемся помочь.
Ошибка чтения каталогов
Попробуйте подключиться через меню Файл — Менеджер сайтов, а не через быстрое подключение. В настройках подключения выберите SFTP, 22 порт.