Troubleshooting 79
Solution 2
Make sure the routing to the Virtual Private Server is properly configured. Virtual Private
Servers can use the default router for your network, or you may configure the Hardware Node
as rooter for its VPSs.
Failure to Log In to VPS
The Virtual Private Server starts successfully, but you cannot log in.
Solution 1
You are trying to connect via SSH, but access is denied. Probably you have not set the password
of the
root
user yet or there is no such user. In this case, use the
vzctl set --save --
userpasswd
command. For example, for Virtual Private Server 101 you might issue the
following command:
# vzctl set 101 --save --userpasswd root:secret
Solution 2
Check forwarding setting by issuing the command:
# cat /proc/sys/ipv4/conf/venet0/forwarding
If it is 0 then change it to 1 by issuing the command:
# echo 1 > /proc/sys/ipv4/conf/venet0/forwarding
Problems with VPS Operation
Timeout When Accessing Remote Hosts
A host is unreachable by the OpenVZ Hardware Node or its Private Servers, though it can be
reached from other computers.
Solution
Often these timeouts occur due to the fact that the Explicit Congestion Notification (ECN)
mechanism of the TCP/IP protocol is on by default in OpenVZ and off in some other systems,
which leads to their incompatibility. ECN is used to avoid unnecessary packet drops and for
some other enhancements. If OpenVZ cannot connect to a host, turn off this mechanism:
# sysctl –w net.ipv4.tcp_ecn=0
net.ipv4.tcp_ecn = 0