Skyline Health Diagnostics UI not accessible after deploying appliance version 2.5.0-18059916_OVF10

[ajashraf]

Get message: This site can’t be reached

refused to connect.

When i deployed the appliance, i was able to change the root password successfully.

I am able to use putty and SSH to the appliance and login with root with the password which i setup without any issues.

However i am unable to connect to web ui.

Can you please advise?

[ksram]

@ajashraf Can you please login as root and run curl command to check the web services

Run curl -k https://IPOFAPPLIANCE:8443:/api/v1 This should output the version information. If this is running, most likely issue could be network related

[ajashraf]

Using this syntax i am getting the following message:

root@photon [ ~ ]# curl -k https://IP Of Appliance:8443:/api/v1
curl: (3) URL using bad/illegal format or missing URL

[ajashraf]

I have removed the extra : and now get the following:

root@photon [ ~ ]# curl -k https://IP address of Appliance:8443/api/v1
curl: (7) Failed to connect to {IP Address} port 8443: Connection refused

[ajashraf]

root@photon [ /etc/systemd/system ]# systemctl status nginx.service
● nginx.service - Nginx High-performance HTTP server and reverse proxy
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-07-08 10:46:12 UTC; 8min ago
Process: 961 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=1/FAILURE)

Jul 08 10:46:12 photon systemd[1]: nginx.service: Service RestartSec=100ms expired, scheduling restart.
Jul 08 10:46:12 photon systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Jul 08 10:46:12 photon systemd[1]: Stopped Nginx High-performance HTTP server and reverse proxy.
Jul 08 10:46:12 photon systemd[1]: nginx.service: Start request repeated too quickly.
Jul 08 10:46:12 photon systemd[1]: nginx.service: Failed with result 'exit-code'.
Jul 08 10:46:12 photon systemd[1]: Failed to start Nginx High-performance HTTP server and reverse proxy.

[ajashraf · Accepted solution]

OVA redeployed to resolve

[geschnei]

For me the problem seemed to be that the initial shd-admin password didn't match the password rules.

After deployment the appliance wasn't reachable via port 80 or 443, but when I went to https://1.2.3.4:8443/ I was presented with the message that the initial setup couldn't be completed and the option to set a new password.

It turned out that the shd-admin password needs to contain at least one special char, which my first password didn't have. After setting a new password the setup was completed, the appliance rebooted and I was able to reach it via regular HTTP and HTTPS ports.