1-800-691-1991 | 9am - 8pm ET

All Aliases Have Failed


Tenant jobs may fail with the following message:

Target gate has rejected connection. Unable to establish target connection. All aliases have failed.


New cloud infrastructure components have been added, and all gateways are unable to communicate with tenant repositories; or the SP Veeam Server.


It’s important to note that the verbiage of the error may differ, however the root error will be the same. All Aliases Have Failed is the root error message.

To resolve, ensure that all gateway servers available in the service provider infrastructure can communicate with the tenant(s) repository, as well as the SP Veeam Server.

For communication route reference:

User-added image

As a note, private gateways are not recommended, and is one of the more common scenarios to encounter ‘All Aliases Have Failed’. Veeam will attempt to load balance across any available gateway, based on current tenant connections, and a gateway usable by a specific tenant can get selected, resulting in this error. In addition, a private gateway can introduce a 4 minute and 15 second delay on every task (disk) processed by a tenant.
Veeam Cloud Connect
8.x, 9.x
Last Modified:
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.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.