Is this a standalone vRO appliance or vRO embedded in vRA? Could you check if the Kubernetes pods are up and running? To do so, open SSH terminal to the vRO appliance and run the following command:
Did you ever get this resolved? I am seeing the same issue in our lab.
After deploying 8.0.1 appliance and applying the fix from the KB the vco-app container shows as 2/2 Ready, but going to the FQDN URL gives "404 page not found". DNS is working ok on the appliance forward and reverse.
If you get 404 after login and not a login error try manually changing the URL in the browser to https://your_orchestrator_FQDN/orchestration-ui/ after you get to the 404 page.
If this helps could you please share a screenshot of your browser with the 404 error where the current URL is visible?
This had to do with certificates. I had forgotten that in the lab we replaced the default certs with private CA signed certs, and that seemed to break the Orchestrator installation. I deployed a fresh new vCenter 6.7 and configured it as the identity source and the same Orchestrator appliance worked just fine.
