Step 4: Failed to resolve CloudEndure Service Manager address in the replication server

Important! The information provided in this section is for general Troubleshooting guidance only. The information is provided on "AS IS" basis, with no guarantee of completeness, accuracy or timeliness, and without warranty or representations of any kind, expressed or implied. In no event will CloudEndure and/or its subsidiaries and/or their employees or service providers be liable to you or anyone else for any decision made or action taken in reliance on the information provided above or for any direct, indirect, consequential, special or similar damages (including any kind of loss), even if advised of the possibility of such damages. CloudEndure is not responsible for the update, validation or support of troubleshooting information.

Possible causes for failure

1. The subnet selected for the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. is configured in a way that prevents DNS lookups to resolve to console.cloudendure.com. Make sure that DNS traffic is not blocked. Create an machineA physical or virtual computer. in the Replication ServerThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location.’s subnet and try to resolve console.cloudendure.com (either by accessing the destination on your browser or using the following command:
   wget https://console.cloudendure.com/