Hi, and welcome to the community.
Instead of the IP address, you should use the hostname / FQDN of the vRO appliance machine.
Here is the link to the corresponding section of vRO documentation: https://docs.vmware.com/en/vRealize-Orchestrator/8.0/com.vmware.vrealize.orchestrator-install-config.doc/GUID-5349E2AC-93C8-4AEC-939B-313DCA2CA93D.html
Thanks a lot for your information and now i am able to do my workflows.
Hello I will use a Alias to connect to vRO how can I add this Name?
I have on DNS the Alias created but I get also "404 page not found"
Hi, I have the same issue altough I'm using the FQDN.
Could you open a SSH terminal to the appliance and verify if the Kubernetes pods are up and running? If they are not in running state, then the next step would be to check log files for clues/errors.
I see that the vco-app is crashing. How do I see the logs associated with the pod?
Here's an output of the kubernetes pods -
# kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
ingress ingress-ctl-traefik-5674bc8d88-zcdlt 1/1 Running 0 171m
kube-system coredns-wp49l 1/1 Running 0 172m
kube-system endpoints-weight-lbwwr 1/1 Running 0 172m
kube-system etcd-vro8.bcbst.com 1/1 Running 0 172m
kube-system health-reporting-app-qj859 1/1 Running 0 172m
kube-system kube-apiserver-vro8.bcbst.com 1/1 Running 0 172m
kube-system kube-controller-manager-vro8.bcbst.com 1/1 Running 0 172m
kube-system kube-flannel-ds-jl8v8 2/2 Running 0 173m
kube-system kube-proxy-8l5lz 1/1 Running 0 173m
kube-system kube-scheduler-vro8.bcbst.com 1/1 Running 0 172m
kube-system kubelet-rubber-stamp-h4drr 1/1 Running 0 173m
kube-system metrics-server-fzjn2 1/1 Running 0 172m
kube-system predictable-pod-scheduler-lgzx9 1/1 Running 0 172m
kube-system prelude-noop-extnet-ds-dqlv7 1/1 Running 0 172m
kube-system prelude-noop-intnet-ds-w5t7z 2/2 Running 0 172m
kube-system state-enforcement-cron-1581451200-5m6t2 0/1 Error 0 53s
kube-system state-enforcement-cron-1581451200-7bjbt 0/1 Error 0 83s
kube-system state-enforcement-cron-1581451200-mp79f 0/1 Error 0 86s
kube-system state-enforcement-cron-1581451200-vn66x 0/1 Error 0 13s
kube-system state-enforcement-cron-1581451200-vt4hm 0/1 Error 0 73s
kube-system tiller-deploy-d9c8fb4cd-kkbmr 1/1 Running 0 172m
prelude orchestration-ui-app-599876bd55-4wrk4 1/1 Running 0 171m
prelude pgpool-dd778f5dc-qh5nf 1/1 Running 1 171m
prelude postgres-0 1/1 Running 0 171m
prelude symphony-logging-daemonset-28x6z 1/1 Running 0 171m
prelude vco-app-8c9d5c779-b742w 0/2 Init:CrashLoopBackOff 37 171m
Hi, maybe try to wait some more.
It looks to me that after the appliance seems to have started, it takes some time for all the "services" to get started.
I also got the "404 page not found" and "bad gateway" but did manage to log in after some more minutes of patience.
Hope this helps.
Its been 2 days and its still broke. Opened an SR and they suggested to try 8.0.1 and boom!
Works like a charm.
I had the same Problem,
in my case it was because of dns problem.
You can only open the vro page with the name you specified by installation
if host name of the machine is without fqn you need to use it like this!
check dns pointer es well!
ps: there is no voami address like https://server:5480
I imagine some of this is due to the bug referenced here
After updating the yaml file and running deploy.sh the vco service comes up but if you restart the appliance it goes back to crashing until running deploy.sh again.
Really buggy appliance!
after a fresh 8.1.0 deployment i got the "404 page not found" errors when browsing https://fqdn/vco
i had not set hostname to fqdn as instructed
after a redeployment using fqdn i get "bad gateways" errs
i waited until all pods were up prior to attempting to connect