You need to give Orchestrator the same name as the machine that he is running on.
After that, you need to remove all the current certificates, restart the machine and create new certificates (now that you’ve changed the name of the Orchestrator).
You also need to change binding in C:\Windows\System32\drivers\etc\host file (picture shown below)
Restart the machine one more time just to be sure.
After that you can export the certificate and then install it.
You need to change the bindings in your local machine (C:\Windows\System32\drivers\etc\host) as well (as shown in the picture below) so you can access the Orchestartor .
After that, if you can access the Orchestrator with Machine name where it is hosted on, you can probably connect the robot.
Note, you can probably do this with different name than the machine name where Orchestrator is hosted, but I didn’t test it