Error message: “The public IP address is already connected to a running machine.”
This error occurs when a VM shares a static public IP address with another VM that is running.
A static public IP address can be attached to multiple VMs, but it can be deployed by only one VM at a time. The public IP address is deployed when someone runs one of the VMs the public IP is attached to. While the public IP address is deployed, you can’t run any of the other VMs that the public IP address is attached to.
- If you are using an environment that has been shared with you, contact your administrator or instructor. You can’t run the VM until the static public IP address is detached or the static public IP is no longer deployed by another VM.
If you are a Skytap user with permission to edit the environment:
- If you need to run the VM, but don’t need to use the static public IP address, detach the static public IP address from the VM.
- If you can use any public IP address, attach a different static public IP address or attach a dynamic public IP address with a Skytap-managed DNS name.
- If you need to use this specific static public IP address, work with your Skytap administrator to identify the VM that is currently using the public IP address. Coordinate with the other users in your account to make sure only one of the VMs is running at a time.