Power Users

#8: Post edited by (deleted user) · 2021-09-24T11:55:15Z (about 3 years ago)

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
~~## Update_1~~
I think that the problem is now solved.
Namecheap's support staff reported:
> Our technical department has found that the SSH access was not enabled properly for your hosting account:
the cPanel username was not added correctly in whitelist here: /etc/csf/csf.pignore.nc .
As a result, our firewall noticed that some processes kept being open and closed the connection. The cPanel username is added now.
~~To me that makes sense because indeed the problem started after changing a Cpanel username.~~

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update
The problem is now solved.
Namecheap's support staff reported:
> Our technical department has found that the SSH access was not enabled properly for your hosting account:
the cPanel username was not added correctly in whitelist here: /etc/csf/csf.pignore.nc .
As a result, our firewall noticed that some processes kept being open and closed the connection. The cPanel username is added now.
To me that makes sense because indeed the problem started after changing a Cpanel username.
24/09/20: Since writing the update I didn't have the problem at all.

#7: Post edited by (deleted user) · 2021-09-13T06:38:38Z (over 3 years ago)
No longer relevant

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update_1
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.
~~## Update_2~~
I think that the problem is now solved.
Namecheap's support staff reported:
> Our technical department has found that the SSH access was not enabled properly for your hosting account:
the cPanel username was not added correctly in whitelist here: /etc/csf/csf.pignore.nc .
As a result, our firewall noticed that some processes kept being open and closed the connection. The cPanel username is added now.
To me that makes sense because indeed the problem started after changing a Cpanel username.

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update_1
I think that the problem is now solved.
Namecheap's support staff reported:
> Our technical department has found that the SSH access was not enabled properly for your hosting account:
the cPanel username was not added correctly in whitelist here: /etc/csf/csf.pignore.nc .
As a result, our firewall noticed that some processes kept being open and closed the connection. The cPanel username is added now.
To me that makes sense because indeed the problem started after changing a Cpanel username.

#6: Post edited by (deleted user) · 2021-09-13T02:28:04Z (over 3 years ago)

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
~~## Update~~
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update_1
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.
## Update_2
I think that the problem is now solved.
Namecheap's support staff reported:
> Our technical department has found that the SSH access was not enabled properly for your hosting account: 
the cPanel username was not added correctly in whitelist here: /etc/csf/csf.pignore.nc . 
As a result, our firewall noticed that some processes kept being open and closed the connection. The cPanel username is added now.
To me that makes sense because indeed the problem started after changing a Cpanel username.

#5: Post edited by (deleted user) · 2021-09-12T09:48:01Z (over 3 years ago)

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
~~This problem would normally occur less than five mintues after the SSH connection to that environment ; the problem will occur in any such session, whether commands have been executed or not.~~
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment:
* I can experience a disconnection while typing commands
* It doesn't matter if commands have been executed or not
* Changing keepalive value from 0 to 1 didn't help
* A similar problem happens with MobaXterm
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

#4: Post edited by (deleted user) · 2021-09-11T15:56:05Z (over 3 years ago)

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment ; the problem will occur in any such session, whether commands have been executed or not.
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment ; the problem will occur in any such session, whether commands have been executed or not.
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
In that particular case I can bypass the problem by using GUI tools but I still ask this by principle.
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

#3: Post edited by (deleted user) · 2021-09-11T14:30:54Z (over 3 years ago)

Copy Link

Raw

Markdown

~~I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years. ~~
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined with that plan a few months ago.
I normally SSH into my hosting account with Putty (version 0.70). 
My Putty configuration is all default and the SSH connection is being done with a keyphrased private key and public key.
## My problem
~~In the last few days I have started to experience sudden disconnections from Namecheap's server environment with Putty, with the error:~~
> Connection closed by remote host
~~This problem can occur less than a minute after an SSH connection or after about 5 minutes or so ; the problem will occur in any session, whether commands have been executed or not.~~
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years and never had any problem SSHing into various shared hosting environments with Putty.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined there with that plan a few months ago; I normally SSH into that shared hosting environment with an all default Putty 0.70 and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's shared server environment with Putty, with the error:
> Connection closed by remote host
This problem would normally occur less than five mintues after the SSH connection to that environment ; the problem will occur in any such session, whether commands have been executed or not.
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

#2: Post edited by (deleted user) · 2021-09-11T14:22:21Z (over 3 years ago)

Copy Link

Raw

Markdown

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years.
~~I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined with that plan about 4 months ago.~~
~~I normally SSH into my hosting account with Putty. ~~
My Putty configuration is all default and the SSH connection is being done with a keyphrased private key and public key.
## My problem
~~In the last few days I have started to experience sudden disconnections from Putty with the error:~~
> Connection closed by remote host
This problem can occur less than a minute after an SSH connection or after about 5 minutes or so ; the problem will occur in any session, whether commands have been executed or not.
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
~~How would you suggest to cope with that problem?~~

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years.
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined with that plan a few months ago.
I normally SSH into my hosting account with Putty (version 0.70).
My Putty configuration is all default and the SSH connection is being done with a keyphrased private key and public key.
## My problem
In the last few days I have started to experience sudden disconnections from Namecheap's server environment with Putty, with the error:
> Connection closed by remote host
This problem can occur less than a minute after an SSH connection or after about 5 minutes or so ; the problem will occur in any session, whether commands have been executed or not.
## Contacting Namecheap's support
I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.
They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.
Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:
> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).
> The possible solutions are:
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).
## Interim note
I have no desire to use a static IP, nor do I want to use a VPN.
## My question
How would you suggest to cope with that problem?
## Update
When connecting with the same circumstances (same mobile carrier, same mobile plan, same operating system, Putty 0.70 etc.) to another CentOS shared server, that time on SiteGround, I didn't have any issues, but that was just before I have become Namecheap's customer and as mentioned, the problem connecting to Namecheap started just a few days ago. If someone here would allow me to login to its own test environment just to check if it happens there as well, please suggest it in a comment.

#1: Initial revision by (deleted user) · 2021-09-11T11:02:46Z (over 3 years ago)

Copy Link

Raw

Markdown

Connection closed by remote host in Putty with hosting provider says that the problem is not on their side

I use my smartphone as my "router", with dynamic IP addresses, for nearly 3 years.<br>
I host my website on a CentOS based shared server environment by Namecheap (Stellar business plan); I have joined with that plan about 4 months ago.

I normally SSH into my hosting account with Putty.<br>
My Putty configuration is all default and the SSH connection is being done with a keyphrased private key and public key.

## My problem

In the last few days I have started to experience sudden disconnections from Putty with the error:

> Connection closed by remote host

This problem can occur less than a minute after an SSH connection or after about 5 minutes or so ; the problem will occur in any session, whether commands have been executed or not.

## Contacting Namecheap's support

I have tried to contact the customer support of Namecheap and they say that they have tried to SSH into my account from their computer and didn't encounter any problem.

They suggested to reboot the router (my smartphone) and to try again; I did so by principle but it didn't solve the problem.

Namecheap's staff also asked me to execute various `tracert NAMECHEAP_IP` commands from CMD spanning hundreds of lines (hence I avoid pasting it here) and after reviewing all the output they said:

> The issue seems to be caused by a dynamic IP address. It causes a
> logout very soon after logging in via SSH.<br>
> The dynamic IP can be
> provided by your current ISP (or it can be a feature of the VPN
> connection if you use any).<br>
> The possible solutions are:<br>
> 1) Contacting
> your ISP for providing a static IP address or a dynamic IP address,
> but within the same /24 subnet only.<br>
> 2) Configuring a VPN service with
> a static IP (or within /24 subnet as well).

## Interim note

I have no desire to use a static IP, nor do I want to use a VPN.

## My question

How would you suggest to cope with that problem?

ssh cmd putty connection shared-hosting

Communities

Post History