https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTg5IiwiaGFzaCI6IjM4MjJkNDMyLTVjMzAtNGNmNS1hZThkLWZiZGJhNDViMmNhZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

SureBackup: A connection attempt failed

Challenge


Cause

Veeam Backup & Replication is not able to connect to the Virtual Lab and grab network settings from the web server.

Solution

If you assign a proxy appliance an IP address from the same network where the Veeam B&R server is located, Veeam B&R will automatically add a new route to the routing table on the Veeam Backup server, so please make sure that the 443 port is not blocked.

If you assign a proxy appliance an IP address from a network other than that where the Veeam B&R server is located, you will have to manually add a new route to the routing table on the router in the production network. Otherwise, you will not be able to access virtual machines in isolated networks.

Ensure that the specified network settings on the "Proxy" step of the Virtual Lab wizard corresponds to the production settings.

KB ID:
1189
Product:
Veeam Backup & Replication
Version:
5.x, 6.x
Published:
2011-08-25
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later