v0.4.3.1: Connect to VPC Instance Attempts Connections to Internal IP

[kopaka]

This is similar to an issue I raised (and was later resolved) for non-VPC instances last year. It is a minor issue, as there is a workaround.

In the Instances tab, when you right-click on an instance inside a VPC but for which no Elastic IP has been assigned and select Connect to Instance, the connection attempt is made to the internal IP (e.g. 10.0.0.40) instead of the public IP (e.g. 184.73.123.112). This might be as intended.

However, after an Elastic IP has been assigned to the instance, remote connections are still attempted to the internal IP.

The workaround is simply to refresh the entire page, and then subsequent connection attempts are (correctly) made to the instance's public IP address.