Getting 404 - /vco-controlcenter/ when I try to access the configurator. I've tried restarting the configurator. I don't see anything in any logs, either. Where is the log for this, anyway?
I'm using the vRO that comes built-in to vRA 7.2.
Is the service started? It should be accessible at https://<FQDN>:8283/vco-controlcenter/
Yes, it is started. If I try to hit the page with it stopped, I get a 503 Service Unavailable.
Control Center logs are under /var/log/vco/configuration/
The only thing I see in there is a bunch of:
127.0.0.1 - - [18/Sep/2017:10:11:45 -0500] "GET /vco-controlcenter/ HTTP/1.1" 404 1086
in localhost_access_log..txt (yes, two .'s)
All the other log files are about 50 minutes old.
Out of curiosity is your vRA/vRO environment clustered or a single appliance? We are encountering this issue in our clustered setup what seems like intermittently. I've also noticed that if I vpn in from home I don't have an issue its only when I attempt to connect from one of our internal networks. I'm suspecting either a load balancer issue or something weird going on with the vRO/vRA clustering that is masked when I come in through the vpn. I have no issues if I take one of the appliances down. I have to take all the services offline not just the vRO services to get the error to go away.
Mine is a single-appliance/single-IaaS setup. I was considering bouncing the appliance.
Any load balancer in the mix?
I thought the backing MSSQL db might be, but our Windows guys confirmed that it isn't. No LBs at all.