Fresh pi-hole install fails (OMV latest), FTL unable to get latest release location from GitHub

[Bangity]

Please follow the below template, it will help us to help you!

Expected Behaviour:

Running `curl -sSL https://install.pi-hole.net | bash

Actual Behaviour:

Should just work but failed with curl 77. So I tried method 1 & 2 installation as well as -sSLk which proceeded. It failed at FTL Engine (unable to locate latest)

Debug Token:

[curl: (77) error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs]

Things I Tried

sudo apt-get update (successfully)

ca-certificates: This is the latest with OMV (I have another XU4 running with the same cert and latest pihole)
Installed: 20161130+nmu1+deb9u1
Candidate: 20161130+nmu1+deb9u1
Version table:
*** 20161130+nmu1+deb9u1 500
500 Index of /debian stretch/main armhf Packages
100 /var/lib/dpkg/status

curl -si Release v6.0.4 · pi-hole/FTL · GitHub returns empty string but able to wget

Changed /etc/resolv.conf to nameserver 1.1.1.1 (did not help)

I am really confused as both XU4 are running the same OMV version and cert. This XU4 is giving me problem installing pi-hole which installed seemlessly on the other server.

[Mcat12]

You have an error on your system which is unrelated to Pi-hole. Have you tried generally looking online for this error?

[Bangity]

I have exhausted google on this topic. Everyone was able to run pihole -r after changing DNS but pihole command doesn't exist on this system after restart.

I have no idea how to tackle.

[Mcat12]

That command doesn't exist because you didn't install Pi-hole. Your install is failing before any of our code even runs. If Google is no help then try reinstalling your OS.

[Bangity]

The command sudo update-ca-certificates solved the problem. It's strange because the certificates are still the same.

Thank you.

[jfb]

Were you able to install Pi-Hole now?

[Bangity]

Yes, up and running as a redundancy 2nd DNS on router.