Hi, I am running into the same problem. Could you please share or refer to a page with the solution?
As it was referred, LifeTime uses HTTP (80) or HTTPS(443) to communicate with the environment's ServiceCenter. It will try to connect to HTTPS (443) first, and then fallback to HTTP (80).
What is not referred is that the environment's Service Center needs to be able to connect back to LifeTime using the same protocols (port 80 or port 443).
It's also possible to force the registration to use SSL, which will establish a HTTPS (port 443) connection only, not falling back to HTTP (80).
So you need to guarantee that the LifeTime environment reaches the environment/server you're registering, but also the inverse path (the server reaches the LifeTime).
If you're using HTTPS (port 443), make sure you have valid and trusted SSL certificates in the IIS of both the LifeTime environment and the environment/server you're registering.
If you're not using HTTPS, it will fallback to HTTP (port 80).
To validate the connections, you can access the LifeTime server, and open a web browser and access Service Center of the environment being registered. And then access the environment's server and open a web browser and access the LifeTime.
Hope this information is helpful.
In my case i had to install a SSL Certificate and bind port 433 to it.I could not continue without.attached IIS Manager Site Binding screenshot.
Hope it helps.