Warning: Cannot connect to online repository(s) (http://mirror1.freepbx.org,http://mirror2.freepbx.org). Online modules are not available

I am using FreePBX 15.0.16 (distro).
Today I am receiving warnings in the Module Admin, when trying to Check Online. Dashboard tells me there are upgrades waiting. However I get:

Warning: Cannot connect to online repository(s) (http://mirror1.freepbx.org,http://mirror2.freepbx.org). Online modules are not available

If I wget http://mirror1.freepbx.org, then it will download an index.htm file.
If I wget http://mirror2.freepbx.org it cannot find the server.

Using the CLI:

~# fwconsole ma upgradeall
No repos specified, using: [standard,commercial,unsupported,extended] from last GUI settings

Module(s) requiring upgrades: backup, core, filestore, framework, sysadmin, zulu
Upgrading module 'framework' from 15.0.16 to 15.0.16.18
Downloading module 'framework'
Processing framework
Verifying local module download...Redownloading
The following error(s) occured:
 - File Integrity failed for /var/www/html/admin/modules/_cache/framework-15.0.16.18.tgz.gpg - aborting (sha1 did not match)

Also:

~# ping 162.253.134.144
PING 162.253.134.144 (162.253.134.144) 56(84) bytes of data.
^C
--- 162.253.134.144 ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7000ms

~# ping 199.102.239.170
PING 199.102.239.170 (199.102.239.170) 56(84) bytes of data.
64 bytes from 199.102.239.170: icmp_seq=1 ttl=49 time=90.6 ms
64 bytes from 199.102.239.170: icmp_seq=2 ttl=49 time=90.3 ms
64 bytes from 199.102.239.170: icmp_seq=3 ttl=49 time=90.2 ms
^C
--- 199.102.239.170 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 90.281/90.446/90.677/0.297 ms

I note the following entries in the iptables -L: (amongst many others redacted)

Chain fpbxhosts (1 references)
target     prot opt source               destination
zone-trusted  all  --  199.102.239.170      anywhere
zone-trusted  all  --  static.162.253.134.144.cyberlynk.net  anywhere

I am not familliar with the syntax used in the static entry, which lists the IP addess that fails, but this might be a red herring since the first IP address does work. Clearly this is not a DNS issue because I’m pinging the resolved IP addresses, not the URL.

Coincidentally (or not?) I have a separate notice which cautions me that my disk space is low:

Storage space is getting high on the following drives of your system:

/dev/mapper/SangomaVG-root is 75% full

However, according to the dashboard there is 25% left and I very much doubt the files are that big.

I would be grateful for any help in diagnosing this issue.

Kind regards

Andy

It’s down for me as well. Cannot update any of my servers.

1 Like

Known issue - we are working to restore services as quickly as possible

5 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.