Repeated lines in Comet Server system logs with: Error communicating with central server: failed remote telemetry submission: Unexpected HTTP response code: 500 body: Internal error

Symptoms

• The server logs show repeating errors with lines stating:

  CONFIG_TEXT: Error communicating with central server: failed remote telemetry submission: Unexpected HTTP response code: 500 body: followed by Internal error.

• After consistent errors, the server is unable to renew its license lease, and shuts down. Opening the Comet Server web interface URL shows the following message:

  CONFIG_TEXT: The server failed to start properly. Please check the server logs to diagnose the issue.

Cause

Comet Server locks its license to the server's external IP address and hardware ID by default. When either changes (for example after the server is replaced or a dynamic IP changes), the licensing server rejects the license lease renewal with an HTTP 500 error, and the server shuts down once it can no longer renew the lease.

Resolution

1. Relax the license for the affected server. The IP and device ID will be unlocked, then re-locked on the first license lease.

2. If the server is on a dynamic IP address, disable the IP lock.