Skip to main content

Error: "Unable to validate license...The remote server returned an error: (500). Internal Server Error."

This article explains how to resolve a rare error that occurs when CloudM Migrate cannot communicate with the CloudM licensing platform.

1. Symptom

During a license check or at the start of a migration, the process fails with the following error message:

Migration Failed: Unable to validate license, unable to query license server. The remote server returned an error: (500). Internal Server Error.

This indicates that the server running CloudM Migrate was unable to connect to or get a valid response from the CloudM license validation service.

2. Cause

This error is not caused by a problem with your license itself. Instead, it points to a network connectivity issue between your migration machine and the CloudM licensing platform, which is hosted at https://tracker.cloudm.io.

The most common causes are:

  • Firewall Rules: Your corporate firewall is blocking outbound HTTPS (port 443) traffic from the migration server to tracker.cloudm.io.

  • Network Proxy Issues: The migration server is configured to use a network proxy that is not correctly configured or is actively blocking the connection.

  • DNS Resolution Failure: Your local network's DNS server is unable to resolve the IP address for tracker.cloudm.io.

  • Temporary Platform Unavailability: In extremely rare cases, the CloudM licensing platform itself may be experiencing a temporary issue.

3. Resolution

To resolve this issue, you must ensure your migration server can successfully communicate with https://tracker.cloudm.io over HTTPS.

Was this article helpful?
0 out of 4 found this helpful