huxiaoxin
Contributor
Contributor

orchestartor8 http 404

Hello All,

I have successfully deployed the vro 8.0 and when i try to login to the https://your_orchestrator_FQDN/vco, i get the following error:

404 page not found

dns setting is ok.

pastedImage_1.png

8 Replies
iiliev
VMware Employee
VMware Employee

Hi,

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:

kubectl -n prelude get pods

0 Kudos
igaydajiev
VMware Employee
VMware Employee

By vro 8.0 do you refer to vRO 8.0.0 or 8.0.1?
8.0.1 is patch release and I will suggest to start with it.

Not sure if you have already check it. Looks like another user has similar error which got resolved using 8.0.1

Re: vRealize orchestrator 8.0 " 404 page not found"

0 Kudos
huxiaoxin
Contributor
Contributor

the install media is O11N_VA-8.0.1.7355-15296158_OVF10-2

0 Kudos
huxiaoxin
Contributor
Contributor

install with ova files , a standalone vRO appliance

kubectl -n prelude get pods

pastedImage_0.png

0 Kudos
mbrkic
Hot Shot
Hot Shot

Hi,

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.

Cheers,

Milos

0 Kudos
inevp
Enthusiast
Enthusiast

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?

0 Kudos
mbrkic
Hot Shot
Hot Shot

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.

0 Kudos
jonathanvh
Enthusiast
Enthusiast

I had the same issue while installing/configuring vRealize Orchestrator 8.0.1.

You really have to go to the FQDN that you filled in during the deploy of the OVA.

https://FQDN/vco-controlcenter/ or https://orchestrator.homelab/vco/