Unable to watch vRO client web page after successful deployment

[kapily]

I downloaded latest 8.2 build of vRO appliance and deployed it successfully. To see the first web page for vRO client, hit the IP of vRO appliance but did not get any web page..only getting below message..Kindly suggest if i am missing any step.

https://192.168.111.65 

This site can’t be reached

192.168.111.65 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

[mouyaq]

Can you enter into: https://192.168.111.65/vco-controlcenter?

[kapily]

Hey Mouyaq,

I tried to hit URL https://192.168.111.65/vco-controlcenter but still getting same error.

Please find attached snapshot and suggest if i am missing something.

Thanks,

[Jeff_CH]

All vRO websites (client, control center etc.) can only be accessed by the hostname that was provided during the OVF installation.

For instance something like: https://vro.myorg.local

Access through any DNS-aliases won't work either!

[mouyaq]

If you dont receive a warning trying to enter into that url, try to review your dns server and after check all work redeploy the appliance again.

You must enter with dns name, but trying to access to the ip should return at least a certificate warning.

I recommend you do a snapshot, just after deploy the ova and before poweron the appliance for the first time, because there is some scripts executing only the first time.

[kapily]

Thanks Jeff for sharing your ideas.

Redeployed vRO appliance again with dns alias but still not working it..

VM name: in-vro-01

Hostname: in-vro-01.interrait.info

Hit the URL in browser: https://in-vro-01.interrait.info/vco-controlcenter 

Got response:

This site can’t be reached

in-vro-01.interrait.info’s server IP address could not be found.

Try:

• Checking the connection
• Checking the proxy, firewall, and DNS configuration
• Running Windows Network Diagnostics

ERR_NAME_NOT_RESOLVED

[kapily]

Thanks Mouyaq for quick looking.

I tried to run below nslookup commands to verify that vRO_FQDN is returning IP address back or not. Got the below results. I did not add any entry for vRO_FQDN (in-vro-01.interrait.info) in our DNS server as new zone list (A record). Please let me know if i need to add it first in our DNS server. If no then what could be other cause to not working of it.

***********************************************************************************************

root@in-vro-01 [ ~ ]# nslookup 192.168.111.65
** server can't find 65.111.168.192.in-addr.arpa: NXDOMAIN

root@in-vro-01 [ ~ ]# nslookup in-vro-01.interrait.info
Server: 192.168.101.5
Address: 192.168.101.5#53

** server can't find in-vro-01.interrait.info: NXDOMAIN

root@in-vro-01 [ ~ ]# ping 192.168.111.65
PING 192.168.111.65 (192.168.111.65) 56(84) bytes of data.
64 bytes from 192.168.111.65: icmp_seq=1 ttl=64 time=0.650 ms
64 bytes from 192.168.111.65: icmp_seq=2 ttl=64 time=0.073 ms
^C
--- 192.168.111.65 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1013ms
rtt min/avg/max/mdev = 0.073/0.361/0.650/0.289 ms

root@in-vro-01 [ ~ ]# ping in-vro-01.interrait.info
PING in-vro-01.InterraIT.info (192.168.111.65) 56(84) bytes of data.
64 bytes from in-vro-01.InterraIT.info (192.168.111.65): icmp_seq=1 ttl=64 time=0.544 ms
64 bytes from in-vro-01.InterraIT.info (192.168.111.65): icmp_seq=2 ttl=64 time=0.059 ms
^C
--- in-vro-01.InterraIT.info ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1014ms
rtt min/avg/max/mdev = 0.059/0.301/0.544/0.243 ms
root@in-vro-01 [ ~ ]#

[mouyaq]

Yes you need to add direct and reverse resolution into DNS server before deploy the appliance.

The appliance must reach the dns server, and after adding the dns records, check that you resolve appliance dns from the computer where you're trying to open the VRO website. Of course you need access from your computer to the appliance ip at 443 port.

You can also check that port 443 is listening into the appliance. You should see something like this.

root@vro [ ~ ]# netstat -laputen | grep :443tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 48935 8008/kube-proxy

After that If you are still unable to access post the result of this command here:

kubectl get pods --all-namespaces

That will list the status of all pods in vro appliance

[kapily]

Hi Mouyaq,

Please find requested commands output below. It seems there is no entry in result for port 443. What could be reason for it? Kindly help on the same.

root@vro [ ~ ]# kubectl get pods --all-namespaces
W1214 12:49:44.463187 17951 loader.go:223] Config not found: /etc/kubernetes/admin.conf
The connection to the server localhost:8080 was refused - did you specify the right host or port?
root@vro [ ~ ]#

root@vro [ ~ ]# netstat -laputen
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19296 682/sshd
tcp 0 304 192.168.111.65:22 192.168.101.242:60909 ESTABLISHED 0 60368 16338/1
tcp 0 0 192.168.111.65:22 192.168.101.242:60901 ESTABLISHED 0 59994 15563/0
tcp6 0 0 :::5488 :::* LISTEN 0 21625 1174/vami-sfcbd
tcp6 0 0 :::5489 :::* LISTEN 0 21626 1174/vami-sfcbd
tcp6 0 0 :::22 :::* LISTEN 0 19298 682/sshd
udp 0 0 127.0.0.53:53 0.0.0.0:* 77 18399 974/systemd-resolve
udp 0 0 0.0.0.0:5353 0.0.0.0:* 77 18400 974/systemd-resolve
udp6 0 0 :::5353 :::* 77 18402 974/systemd-resolve
root@vro [ ~ ]#

[mouyaq]

Please check this log: /var/log/bootstrap/firstboot for errors.

Is it vro 8.2?

[kapily · Accepted solution]

Thanks a lot Mouyaq to quick respond and pointing to log. Yes it is vRO 8.2.

As per your suggestion, i looked into firstboot.log file and saw script is failing while registering ntp server. I did not pass ntp server IP while deploying vRO ova. It seems ntp server is required parameter so this time i passed ntp server IP while deploying ova file and got the initial vRO web page 😀

Again thanks for helping!!

[mouyaq]

Yes, you can use a public ntp if the appliance reach it.