Hopefully someone internal will wake up and notice the alarms going off, but as the guy that WROTE the Mirror server, it looks like something is wrong with Apache.
The server is accepting connections, but the error ‘503: Service Unavailable’ means that Apache was unable to distribute it to a worker process. Probably just restarting the container will fix it.
However, I’m sure that as soon as someone at Sangoma sees the alerts, they’ll sort it out.
Edit: It looks like it’s only ONE of the mirror servers is down (the old one). If you use the newer https one, it should still be fine.
Just run fwconsole setting MODULE_REPO https://mirror.freepbx.org and you’re good!
[root@freepbx ~]# fwconsole setting MODULE_REPO https://mirror.freepbx.org
Changing "MODULE_REPO" from [http://mirror1.freepbx.org,http://mirror2.freepbx.org] to [https://mirror.freepbx.org]
[root@freepbx ~]# ping mirror.freepbx.org
PING mirror.freepbx.org (199.102.239.8) 56(84) bytes of data.
64 bytes from 199.102.239.8 (199.102.239.8): icmp_seq=1 ttl=42 time=227 ms
64 bytes from 199.102.239.8 (199.102.239.8): icmp_seq=2 ttl=42 time=226 ms
--- mirror.freepbx.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 226.692/226.913/227.135/0.525 ms
[root@freepbx ~]# fwconsole ma listonline
No repos specified, using: [standard] from last GUI settings
+----------------------+------------+-----------------------------------+-------------+
| Module | Version | Status | License |
+----------------------+------------+-----------------------------------+-------------+
| accountcodepreserve | 13.0.2.2 | Enabled and up to date | GPLv2 |
| amd | 13.0.3 | Enabled and up to date | GPLv3+ |
| announcement | 13.0.7.7 | Enabled and up to date | GPLv3+ |
| areminder | 14.0.4.2 | Disabled | Commercial |
| arimanager | 13.0.5.3 | Enabled and up to date | GPLv3+ |
... etc ...