my vServer 's ipv6 address is 2a02:0180:0006:0001:0000:0000:0000:49ca.
Customer ID: 13220732 Contract: 380325.
After the reinstallation, I didn't change anything. But it became unreachable .
- September 25, 2023, 03:36:08 PM
- Welcome, Guest
51
VPS / virtual private servers / Virtual servers - general / VS2-free 2.1 became unreachable in 30 hours just after the reinstallation
on: June 28, 2022, 07:34:20 AM
|
||
Started by loulz - Last post by loulz | ||
52
VPS / virtual private servers / Virtual servers - general / Re: VS2-free 2.1 can not complete the reinstallation
on: June 28, 2022, 07:29:36 AM
|
||
Started by loulz - Last post by loulz | ||
Hello, I am sad that it becomes unreachable again, just after the reinstallation and I didn't change anything,which means the new installed OS will became unreachable. |
53
VPS / virtual private servers / Virtual servers - general / Re: VS2-free 2.1 can not complete the reinstallation
on: June 27, 2022, 09:48:46 AM
|
||
Started by loulz - Last post by Forum-Support2 | ||
Hello,
this server is installed atm with CentOS7 and is reachable with ICMP. |
54
VPS / virtual private servers / Virtual servers - general / Re: VS free 2.1 repeatedly becomes unreachable
on: June 26, 2022, 03:09:27 PM
|
||
Started by sbrs - Last post by loulz | ||
Even if I have reinstall my os, it will still be unreachable in 12 hours. I will try not to install anything to check if it will be unreachable
|
55
VPS / virtual private servers / Virtual servers - general / Re: VS2-free 2.1 can not complete the reinstallation
on: June 25, 2022, 12:38:12 PM
|
||
Started by loulz - Last post by loulz | ||
After applying for reinstallations several times, it finally worked. The issue was solved
|
56
VPS / virtual private servers / Virtual servers - general / Re: VS free 2.1 repeatedly becomes unreachable
on: June 22, 2022, 02:43:44 PM
|
||
Started by sbrs - Last post by loulz | ||
I am in the same situation a few days ago. And my operating system is centos 8.
I tried to solve it by installing NetworkManager,but I failed. I coudn't reach the server even if I webreboot the server. After that, I decided to reinstall the OS to Rocky 8. But the disaster happened , the reinstalltion can't complete. |
57
VPS / virtual private servers / Virtual servers - general / VS2-free 2.1 can not complete the reinstallation
on: June 22, 2022, 12:04:43 PM
|
||
Started by loulz - Last post by loulz | ||
my vServer 's ipv6 address is 2a02:0180:0006:0001:0000:0000:0000:49ca.
Customer ID: 13220732 Contract: 380325 I have tried many times, and there is a scheduled job of power off. Scheduled Jobs Queue ID Type Scheduled Date 3242051 Power off 2022-06-20 05:04:03 CEST I hope to reinstall my vserver to Rocky Linux 8 as soon as possbile. Thanks for help. |
58
VPS / virtual private servers / Virtual servers - general / Re: VS free 2.1 repeatedly becomes unreachable
on: June 22, 2022, 08:22:13 AM
|
||
Started by sbrs - Last post by sbrs | ||
I have now disabled all services, rebooted, server was reachable again although no routes were shown. After some time the server again became unreachable so that I could not even ssh into it on IPv6.
Is it normal that no routes are shown in these VS? How can it be reachable without even a default gateway? My server's IPv6 address is 2a02:180:6:1::8a2 Thanks |
59
VPS / virtual private servers / Virtual servers - general / Re: VS free 2.1 repeatedly becomes unreachable
on: June 21, 2022, 09:41:24 AM
|
||
Started by sbrs - Last post by sbrs | ||
After reboot there are no routes at all, even though the link is up and /etc/network/interfaces seems to configure routes. This file seems to be pre-provisioned, i.e. not changed by me. See attachment.
When the problem occurs, the VS is not reachable through the web console so I cannot check for routes. ![]() The VS only runs nginx, no database, nothing else. |
60
VPS / virtual private servers / Virtual servers - general / Re: VS free 2.1 repeatedly becomes unreachable
on: June 20, 2022, 11:45:55 AM
|
||
Started by sbrs - Last post by Forum-Support2 | ||
Hello,
we recommend to check, if your issue is network related or not. We recommend to do the following: 1.) Deactivate all services except SSH. 2.) Wait if issue occurs again. If issue occurs again, please compare the routes (if you have) before the issue occurs first time and now. If nothing help, please post IPv6 here. |