Im using:
Downloaded from: Download VMware vSphere
Build: 10110089
Hostname used during deployment: namevro02_test.domain
My steps:
1. Deployed vRO from OVA
2. Used page https://IP:8283/vco-controlcenter/config
3. On first page "host settings" configured hostname to FQDN or name
.4 Next during saving Authentication provider every time receiving error:
Type Status Report
Message Service Unavailable
Description The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
Rebot not resolving problem. For workaround for now i can only back to previous snapshoot.
Problem is not exist if we are using IP during Hostname configuration on first wizard page.
Some suggestion ?
Sebastian
vSebastian.net
OK we resolved problem by using HOSTNAME(fqdn) without _ "underscore"
Previous i had:
somenamevro2_test.fqdn
Now we have:
somenamevro2test.fqdn
and looks like is working and error 503 not appeared.
Thanks
Sebastian
If this is an external vRO, the port should be 8281 and not 8283 (for Control Center only).
Interesting... but with 8281 is that same...
And yes this is separate VM (vRO appliance).
Sebastian
Yes, 8281 is the TCP port for the main vRO service.
OK we resolved problem by using HOSTNAME(fqdn) without _ "underscore"
Previous i had:
somenamevro2_test.fqdn
Now we have:
somenamevro2test.fqdn
and looks like is working and error 503 not appeared.
Thanks
Sebastian
Hello,
Sometimes one wrong character can cause an error in vRO. It's good to know in the future how to solve a problem like You had. Thanks for reporting how You dealt with this problem. Good tip for the future.
Regards
Michał
cmichal.com
I've got this "Service unavailablie" error after VM HW Upgrade from 13 (esx 6.5) to 18 (esx 7.0.1).
My issue ws fxed by doing the SED things mentioned here:
https://kb.vmware.com/s/article/76870
Regards Steffen