Overview
After the configuration is complete, you may fail to connect the Bastionhost to the Bastionhost. This topic describes the common scenarios where you cannot connect to Bastionhost and the corresponding solutions.
Detail
The common scenarios and solutions for failed Bastionhost connection are as follows. Use the following steps based on your needs.
Problem description |
Solution |
You cannot log on to the Bastionhost by using a public IP address. |
Check the internet access control option in the Bastionhost configuration. Make sure that the Internet access mode is enabled or the IP address you want to use for logon is added to the Internet whitelist.
|
You cannot log on to the Bastionhost by using an internal IP address. | In this case, check whether your client can connect to the Bastionhost over the internal network. If the two ECS instances can be connected, you need to log on to the Virtual Private Cloud system from other ECS instances that are in the same Bastionhost environment. If the login is successful, check the VPN server. Note: if the network type of the Bastionhost is classic network, check for any restrictions on intranet access control in the network configuration. |
You cannot connect to the public IP address of the ECS instance by using Bastionhost. |
Try to access the public IP of the ECS instance without using the Bastionhost system.
|
The internal IP address of the ECS instance that cannot be connected through Bastionhost. |
Check whether the Bastionhost instance and the target ECS instance are in the same Virtual Private Cloud or classic network.
|
Application scope
- Bastionhost