FreePBX repository's down?

Module updateing results at this moment (saturday) in:

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

Is there maintenance?

Hi @4allbusiness loooks good at my end. Could you please recheck ? thanks.

root@ucc-61601996 ~

ping mirror1.freepbx.org

PING mirror1.freepbx.org (199.102.239.170) 56(84) bytes of data.
64 bytes from 199.102.239.170 (199.102.239.170): icmp_seq=1 ttl=49 time=275 ms
64 bytes from 199.102.239.170 (199.102.239.170): icmp_seq=2 ttl=49 time=274 ms
64 bytes from 199.102.239.170 (199.102.239.170): icmp_seq=3 ttl=49 time=274 ms
64 bytes from 199.102.239.170 (199.102.239.170): icmp_seq=4 ttl=49 time=274 ms
64 bytes from 199.102.239.170 (199.102.239.170): icmp_seq=5 ttl=49 time=274 ms
^C
mirror1.freepbx.org ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 274.751/274.902/275.228/0.175 ms

I had this issue and had to update the repo by running:

fwconsole setting MODULE_REPO https://mirror.freepbx.org

I also had to do this to fix the issue as described in this thread: Cannot Connect to Online Repository (mirror1.freepbx.org, mirror2.freepbx.org). It was working fine until I ran a fwconsole restart the other day.

Ping was working also, but there was no service behind the ping.
But now, 18:30 it is all good again.
mirror1 and mirror2 where both down.
I think this was maintenance on the repo.
Thanks for your answer.

Looks like what I and others were seeing two Saturdays ago:

Is Saturday maintenance day for the mirrors?

[ EDIT ]

Just checked freepbx.log and found this (times are EDT):

[2020-Apr-25 05:20:03] [ERROR] (libraries/modulefunctions.class.php:3152) - Failed to get remote file, error was: Failed connect to mirror1.freepbx.org:80; Connection refused
[2020-Apr-25 05:20:03] [ERROR] (libraries/modulefunctions.class.php:3166) - Failed to get remote file, mirror site may be down: http://mirror1.freepbx.org/version-14.0.13.29.html
[2020-Apr-25 05:22:10] [ERROR] (libraries/modulefunctions.class.php:3152) - Failed to get remote file, error was: Failed connect to mirror2.freepbx.org:80; Connection timed out
[2020-Apr-25 05:22:40] [ERROR] (libraries/modulefunctions.class.php:3166) - Failed to get remote file, mirror site may be down: http://mirror2.freepbx.org/version-14.0.13.29.html
[2020-Apr-25 05:22:41] [ERROR] (libraries/modulefunctions.class.php:3152) - Failed to get remote file, error was: Failed connect to mirror1.freepbx.org:80; Connection refused
[2020-Apr-25 05:22:41] [ERROR] (libraries/modulefunctions.class.php:3166) - Failed to get remote file, mirror site may be down: http://mirror1.freepbx.org/all-14.0.xml
[2020-Apr-25 05:24:49] [ERROR] (libraries/modulefunctions.class.php:3152) - Failed to get remote file, error was: Failed connect to mirror2.freepbx.org:80; Connection timed out
[2020-Apr-25 05:25:19] [ERROR] (libraries/modulefunctions.class.php:3166) - Failed to get remote file, mirror site may be down: http://mirror2.freepbx.org/all-14.0.xml

[ EDIT ]

Just had a thought. By default FreePBX checks for updates on Saturday between 4:00 AM and 7:59 AM inclusive, local time. The hour and minute are chosen at random. See Admin->Module Admin->Scheduler and Alerts. I imagine most people haven’t changed this time setting, or more specifically, the day of the week. Are the servers simply getting overloaded on Saturdays?

One of our upstream providers performed some maintenance that had some wider spread impacts than they previously had anticipated. They were able to get it resolved, but it took a bit longer than I think anybody was comfortable with.

Things should be back to normal, but if there are any outstanding problems still, feel free to let us know.

Best wishes, and sorry about the trouble.

Matthew Fredrickson

I am now experiencing this after running a round of updates. I have rebooted and tried even changing the mirrors but I can no longer run updates and have 9 modules apparently uninstalled now.

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