Today we will learn how to fix VPS Connection Problem. In this context, we will learn how to solve Windows and Linux VPS connection problems. VPS connection problems with servers have always been annoying for completely different reasons, even when using servers for specific purposes. Usually, most of the time, even for minor reasons, make us spend a lot of time finding solutions to every problem for a rich and stable connection.
In this article, we have tried to explore most of the major VPS connection issues that cause the server to crash and provide available solutions for them; We hope this article will help you solve these annoying connection problems; First, we will explain the connection problems of each virtual server separately and then we will also examine the sub-problems and solutions.
Why does my VPS connection failing?
The problems are not limited to errors in RDP. That causes us to lose server connections. Other sub-factors include losing a stable connection to the server due to internet interruption, company server disruption, a VPS provider, or an operating system disruption through which you are trying to access your server can also cause you to lose your connection. On the server.
Windows VPS connection issues
It is good to remember: RDP is the same for all versions of Windows Server, so we will see the same error in Windows Virtual Server. Also, when trying to connect to a Windows VPS, sometimes, apart from the main RDP issues, our VPS disconnects from the server due to sub-cases.
In the following sections, we will describe some cases, including:
- RDP is the default port
- Insufficient permissions
- Double user access to RDP
- Use additional bandwidth
Linux VPS connection issues
We may be familiar with the main reasons for our disconnection with Linux servers; In fact, the main problems with connecting to servers in Linux and Windows versions are due to various reasons; As mentioned in the previous section, sub-items also mostly affect RDP connections, but on Linux servers, most of these connection errors are caused by the Putty program itself, which causes us to lose our connection to the server; In the following, we will reveal some of these cases as well as ways to solve them:
- Just showing a blank screen when trying to log in (SSH)
- Putty fatal error: line 11
- Putty Fatal Error: Connect multiple times
- And also, the Putty connection timed out error
Now, we will check each connection error described and also check some main questions we may have:
Windows VPS Main Connection Problems
- Insufficient permissions
- RDP default port
- Double user access
- Consume extra bandwidth
Insufficient permissions
In some cases, to work with some parts of Windows Server, the connection to the Windows VPS server is interrupted, so you need to allow Terminal Services through Remote Desktop Services. Sometimes, if the license is not sufficient to connect to the remote source, the user will encounter errors, and its result may be insufficient permission to connect.
Mostly affected with Windows Server 2016.
RDP is the default port
When connecting to a Windows server through a port other than the main RDP port, sometimes you may lose your connection to the server; Because a network firewall in front of the server only allows connections to the server’s default port will block access to the server!
Dual user access
Suppose you have the same username as the 2nd user or try using more users with limited user access on the server set by the VPS server providers. In that case, RDP warns you: Another user is connected to the remote, so you lose your connection. Try to connect again, or you can contact the network administrator or technical support group.
Consume extra bandwidth
When working with RDP, some programs require more bandwidth that may be due to a lack of available bandwidth, and allocating a lot of bandwidth in cases that improve graphics quality or do not have a specific need for high bandwidth; When working with the program causes Internet speed and even disconnects the server, And you need to restart the service or program on the server.
Windows VPS Connection Problem Solution
Insufficient permissions solution
Open the Group Policy Object Editor tool first then go to the following path;
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
Click: Allow logging in through Remote Desktop Services.
Now add required permissions and click Add required group, then click OK.
RDP default port problem solutions
If there is a network firewall in front of the server, we need to change the remote desktop port to the default: 3389!
First, we will run Windows Registry Editor and then;
Using the following address URL, we can access the remote desktop port number key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
Open the Port Number key and change the base option to decimal; Then set the value data as 3389 after applying the changes; Now the system should restart.
Dual user access problem solution
First, you need to go to the following address at the bottom of your server;
Go to all programs then click > Administrative Tools > Remote Desktop Services > Remote Desktop Session > Host configuration
Next, you need to leave the settings to restrict each user to a single session option on the NO section.
If you see the same error again, you must contact your VPS service provider ASAP.
Consume extra bandwidth
Close applications that may consume additional bandwidth;
Generally, using a lower display resolution or color depth and disabling visual features can significantly increase connection speed and have a stable connection on a Windows VPS.
You can access the Experience and Display headers in RDP to adjust your performance settings in the section below or uncheck them to speed up your connection.
Linux VPS Connection Problem
( PUTTY ) PROBLEMS
1. Putty showing a blank screen when trying to login (SSH)
In this case, you will usually encounter an error that warns you that “Putty Network Error: Caused by software
Connection canceled
These errors usually occur when the page inserted in PuTTY is inactive for a long time and no commands are used.
2. Putty fatal error on line 11
This error contains:
- SSH requires agent forwarding to connect using a public key over TCP.
- Public-key authentication over SSH TCP is not allowed.
When public-key authentication is not enabled for the TCP service or even if the putty agent is not configured to allow forwarding, we typically see these errors on Debian servers!
3. Connect multiple times
Usually when you try to connect to a Linux server several times in a row; If we look closely: Linux-based security programs, such as Fail2Ban and LFD, block certain IPs to prevent brute force attacks. In some cases, your IP may be blocked, for example, when an email tool, FTP tool, or SSH tool contains incorrect login details, the IP is stored as a blocklist in Linux-based special security programs: Fail2Ban and LFD.
4. Putty connection timeout error
The error in the first number described sometimes appears in the second case; We will encounter an error warning as “PuTTY Network Error: Connection Timed Out”.
1. ( PUTTY ) SOLUTIONS
- Just showing a blank screen in putty when trying to log in (SSH)
To avoid the error you noticed, you should first edit the sshd_config file as the root user:
Find the ClientAliveInterval file using the VIM command or the NANO command;
Use one of the commands below to change the ClientAliveInterval file value to 60:
vim /etc/ssh/sshd_config
nano /etc/ssh/sshd_config
Now restart VPS;
For CentOS 7:
systemctl restart sshd.service
CentOS 5/ 6 , RHEL 5/ 6:
service sshd restart
We just set a timeout interval to 60 seconds; This means: that if we become inactive again for a certain period of time, the server will resume connection for 60 seconds, and after that; If no information or response is received from the client, the server will drop the connection and automatically warn a timeout error again!
2. Putty fatal error on line 11
We can enable the agent forwarding option to solve the problem;
We need to use the following address for Putty and enable the agent forwarding option:
Connect > SSH > Authentication > Allow Agent Forwarding
For the second warning error, you need to open the TCP service and check or must enable the public-key authentication option.
3. Connect multiple times
- Sign in again, in this case, security services will usually mistakenly detect and block your IP for brute force attacks.
- If the client’s IP is blocked, contact your service provider and ask them to check the firewall logs; Then, your service provider will reset the login details and resolve the error.
4. Putty connection error timed out
- Open Putty General Configuration.
- Step 2: In the left category list section, select Connections.
- Step 3: In the field ‘KeepAlive in seconds (0 to stop)’, enter 20.
- Step 4: Check the box for ‘Enable TCP Keepalives (SO_KEEPALIVE option).
In this method, the service is inactive after a specified time each time it disconnects from the server; It is renewed every 20 seconds and the connection is static.
If you want to know what is the remote desktop protocol then you can read this content.
