The “connection closed by remote host” message usually indicates that the remote host (e.g., a server) has closed the connection.<\/p>\n
This can happen for a variety of reasons, such as network issue, the remote host crashing, the connection timing out, or the remote host intentionally closing the connection.<\/p>\n
If you are trying to establish a connection to a server and seeing this message , you may need to check if the server is up and running and try again later.<\/p>\n
In this article, I will explain how to troubleshoot this issue. Hopes it can help you fix the issue.<\/p>\n
Make sure that the server you are trying to connect to is online and available. You can try pinging the server to see if it is reachable.<\/p>\n
To use the ping command, open a command prompt or terminal window and type ping followed by the IP address or domain name of the target device. For example:<\/p>\n
ping google.com<\/p>\n
This will send a series of four ICMP echo requests to google.com, and then display the results. The output will show the round-trip time (RTT) for each request, as well as the minimum, maximum, and average RTT.<\/p>\n
Here is an example of the output you might see:<\/p>\n
Ping statistics for 172.217.167.110: From the response, we can get a idea that remote host is up or not. Just be aware that some devices may have ICMP echo request blocking enabled for security reasons.<\/p>\n If this is the case, we can use other options to check it.<\/p>\n We can use some commands like telnet or nc to check the service status on remote server.<\/p>\n For example, to check if the HTTP port (port 80) is open on a remote server with the IP address 192.168.1.1, you can use the following command:<\/p>\n telnet 192.168.1.1 80 Trying 192.168.1.1… If the port is not open, you will see an error message like this:<\/p>\n Trying 192.168.1.1… You can also use the nc (Netcat) command to check if a port is open. For example:<\/p>\n nc -zv 192.168.1.1 80 Connection to 192.168.1.1 80 port [tcp\/http] succeeded! nc: connect to 192.168.1.1 port 80 (tcp) failed: Connection refused<\/p>\n If you can not connect to the remote port, there may be a problem with your network connection or the service that the remote host is on. Try troubleshooting your network connection and see if that resolves the issue.<\/p>\n The firewall on the remote host or on your local machine may be blocking the connection. Check the firewall settings and make sure that the connection is allowed.<\/p>\n There are a few different ways to check the status of the firewall on a Linux machine:<\/p>\n ufw (Uncomplicated Firewall) is a user-friendly firewall that is installed by default on many Linux distributions. To check the status of ufw, use the status command: This will show you whether ufw is active or inactive, as well as the rules that are currently in place.<\/p>\n If ufw is not installed on your machine, you can use the iptables command to check the firewall rules. To see the current firewall rules, use the -L flag:<\/p>\n sudo iptables -L<\/p>\n This will show you the rules that are currently in place for the different chains (INPUT, FORWARD, and OUTPUT).<\/p>\n Alternatively, you can use the firewall-cmd command, which is part of the firewalld service. To check the status of the firewall, use the –state flag:<\/p>\n sudo firewall-cmd –state<\/p>\n This will show you whether the firewall is running or not. To see the current firewall rules, use the –list-all flag:<\/p>\n sudo firewall-cmd –list-all<\/p>\n This will show you the rules that are currently in place for the different zones.<\/p>\n There are some utilities that allow you to view log files on a remote server directly from your local machine. Examples include tail -f, which allows you to view the live output of a log file as it is written to.<\/p>\n For example, if your issue is related to SSH. You can use the tail command to view the contents of log file in real-time:<\/p>\n tail -f \/var\/log\/access.log<\/p>\n This will show you the live output of the access.log file as it is written to. You can use CTRL+C to stop the tail command and return to the command prompt.<\/p>\n If you are looking for specific SSH login events, you can use the grep command to search for them:<\/p>\n grep “sshd” \/var\/log\/auth.log<\/p>\n This will show you all of the log entries that contain the string “sshd”, which should include most SSH login events.<\/p>\n You can also use the journalctl command to view the system log, which includes log entries from the SSH daemon and other system services. To view the log entries for the SSH daemon, use the -u flag to filter by unit name:<\/p>\n journalctl -u sshd journalctl -u sshd –since “1 hour ago” There are many tools available that can help you collect, analyze, and view logs from remote servers.<\/p>\n These tools can often be configured to forward logs from the remote server to a central location, where you can view them in a web interface or through a command-line interface.<\/p>\n Some applications have a limit on the number of users who can access the system concurrently. When the limit is reached, new users will not be able to access the system until one of the existing users logs out or the limit is increased.<\/p>\n Here is an example of error connection closed by remote host. It is related with SSH.<\/p>\n The MaxStartups option in the sshd_config file is used to control the maximum number of unauthenticated connections that the Secure Shell (SSH) daemon will accept at a time. When the number of unauthenticated connections exceeds this limit, the SSH daemon will close new connections until the number of unauthenticated connections falls below the limit again.<\/p>\n The MaxStartups option is used to prevent Denial of Service (DoS) attacks, in which an attacker attempts to overwhelm the system by making a large number of connections. By limiting the number of unauthenticated connections, the MaxStartups option can help to protect the system against these types of attacks.<\/p>\n You can adjust the MaxStartups option to suit the needs of your system. A lower value will increase security but may also result in legitimate users being unable to connect if the connection rate is high. A higher value will allow more users to connect but may also make the system more vulnerable to DoS attacks.<\/p>\n sshd(8) will refuse connection attempts with a probability of rate\/100 (30%) if there are currently start (10) unauthenticated connections.<\/p>\n A busy system can trigger a “connection closed by remote host” error. If a system is under a heavy load, it may not have the resources available to accept new connections or process requests from existing connections. This can cause the system to close connections or refuse new connections.<\/p>\n There are a few different ways you can check if a system is busy:<\/p>\n Check the system load: You can use the uptime command to check the current and average system load. A high load average may indicate that the system is busy.<\/p>\n Check the CPU usage: You can use the top or htop command to check the CPU usage of individual processes. If a single process is using a high percentage of CPU resources, it may be causing the system to be busy.<\/p>\n ps: The ps command is a utility that shows the currently running processes. To see a list of processes sorted by CPU usage, use the -o flag to specify the %CPU column, and use the -aux flags to show all processes for all users:<\/p>\n ps -aux –sort=-%cpu<\/p>\n This will show you a list of processes, sorted by CPU usage in descending order.<\/p>\n If you identify a process that is using a high amount of CPU resources, you can try to identify why it is using so much CPU and see if there is a way to optimize it. You can also use the kill command to terminate the process if necessary.<\/p>\n Check the memory usage: You can use the free command to check the memory usage of the system. If the system is running low on memory, it may be swapping heavily to disk, which can cause the system to slow down.<\/p>\n If you identify that the system is busy, you may need to optimize the processes that are using the most resources or add more resources (such as CPU or memory) to the system to improve its performance.<\/p>\n","protected":false},"excerpt":{"rendered":" The “connection closed by remote host” message usually indicates that the remote host (e.g., a server) has closed the connection. This can happen for a variety of reasons, such as network issue, the remote host crashing, the connection timing out, or the remote host intentionally closing the connection. If you are trying to establish a …<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"disable-in-feed":false,"article-schema-type":"","disable-critical-css":false,"footnotes":""},"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts\/943"}],"collection":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/comments?post=943"}],"version-history":[{"count":0,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/posts\/943\/revisions"}],"wp:attachment":[{"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/media?parent=943"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/categories?post=943"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sslhow.com\/wp-json\/wp\/v2\/tags?post=943"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Pinging google.com [172.217.167.110] with 32 bytes of data:
\nReply from 172.217.167.110: bytes=32 time=26ms TTL=55
\nReply from 172.217.167.110: bytes=32 time=25ms TTL=55
\nReply from 172.217.167.110: bytes=32 time=25ms TTL=55
\nReply from 172.217.167.110: bytes=32 time=26ms TTL=55<\/code><\/p>\n
\nPackets: Sent = 4, Received = 4, Lost = 0 (0% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 25ms, Maximum = 26ms, Average = 25ms<\/p>\nCheck if the service is running on remote server<\/h2>\n
\nIf the port is open, you will see something like this:<\/p>\n
\nConnected to 192.168.1.1.
\nEscape character is ‘^]’.
\nPress CTRL + ] and then type quit to exit.<\/p>\n
\ntelnet: Unable to connect to remote host: Connection refused<\/p>\n
\nIf the port is open, you will see something like this:<\/p>\n
\nIf the port is not open, you will see something like this:<\/p>\nCheck the firewall settings<\/h2>\n
\nsudo ufw status<\/p>\nCheck application log on remote server<\/h2>\n
\nThis will show you the log entries for the SSH daemon. You can use the –since and –until flags to specify a time range for the log entries. For example:<\/p>\n
\nThis will show you the log entries for the SSH daemon from the past hour.<\/p>\nCheck application configuration on server<\/h2>\n
Check system load on server side<\/h2>\n