Install script fails

CentOS Linux release 7.9.2009 (Core)

yum install wget -y
 wget https://raw.githubusercontent.com/VitalPBX/VPS/master/vps.sh
chmod 755 vps.sh
./vps.sh
...
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
       upstream. This is most often useful if you are using a newer
       distribution release than is supported by the repository (and the
       packages for the previous distribution release still work).

    3. Run the command with the repository temporarily disabled
           yum --disablerepo=<repoid> ...

    4. Disable the repository permanently, so yum won't use it by default. Yum
       will then just ignore the repository until you permanently enable it
       again or use --enablerepo for temporary usage:

           yum-config-manager --disable <repoid>
       or
           subscription-manager repos --disable=<repoid>

    5. Configure the failing repository to be skipped, if it is unavailable.
       Note that yum will try to contact the repo. when it runs most commands,
       so will have to try and fail each time (and thus. yum will be be much
       slower). If it is a very temporary problem though, this is often a nice
       compromise:

           yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

@larlap,

That’s something with the network where your PBX is located. I just installed it on D.O a couple of minutes ago and everything is working as expected.

It seems that the system cannot retrieve the info for the “epel” repo; this happens when your network configurations are not the right ones or you have a firewall/proxy blocking the outbound traffic.

CrownCloud tech support said to run following three commands prior to running vps.sh. From his email,

We believe the issue is to do with CA certificate being obsolete by Let’s Encrypt and causing issues with some of the repositories from centos.

yum --disablerepo=epel -y update  ca-certificates
yum clean all
yum update

Did those instructions help?