I’m seeing the same thing. Also bad timing as I had to roll back to a snapshot from four days ago (managed to lock myself out of the system) and I know that a bunch of modules had been updated in that time span.
Edit - forgot that I’d had this problem once before but that time the mirrors came back up before I saw the reply or had a chance to try the proposed solution. Well I tried it today, and it works!
So it looks like mirror2.freepbx.org is the offending repository, as pings do work to mirror1. I tried all the various old tricks to clear the issue and confirmed it isn’t blocked by my firewall.
I further confirmed that iptables on the freepbx instance correctly has the IPv4 /32 for both mirror1 and mirror2 in the fpbxhosts chain as -j zone-trusted
Hopefully someone at Sangoma will look into:
What’s up with the mirrors
Do things work fine just using mirror1 while mirror2 is offline?
I’m also having this issue. No recent updates and was planning an update to v15 today. I’m running v14.0.13.12.
I’ve also tried all the usual steps. I ran fwconsole ma updateall and that ran without issue. I also ran a wget to mirror 1 and that timed out - but the ip was resolved.
Good to know it’s not just my system having issues.
$ fwconsole ma install pm2
Installing/Updating Required Libraries. This may take a while…The following messages are ONLY FOR DEBUGGING. Ignore anything that says ‘WARN’ or is just a warning
npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.
Installed npm-cache v0.7.0
Running installation…
[npm-cache] [INFO] using /home/asterisk/.package_cache as cache directory
[npm-cache] [INFO] [composer] Dependency config file /var/www/html/admin/modules/pm2/node/composer.json does not exist. Skipping install
[npm-cache] [INFO] [npm] using package-lock.json instead of package.json
[npm-cache] [INFO] [npm] config file exists
[npm-cache] [INFO] [npm] cli exists
[npm-cache] [INFO] [npm] hash of /var/www/html/admin/modules/pm2/node/package-lock.json: 8f54767c7dcc88e7626d45dee6f459c8
[npm-cache] [INFO] [npm] running [npm install]…
Well, my issue started only after the mirrors went down, and it’s not the proxy setting.
It’s 4AM here now so I need to give up and try again in the morning!
I am trying to update FreePBX from 12 to 13 and this is causing me problems. I am at the last step running this script and it cant find the mirror1 and 2. How can i update it in the CLI so i cant complete the upgrade? https://upgrades.freepbxdistro.org/stable/10.13.66/upgrade-10.13.66-1.sh
Also - the sipsettings install (part of the core install - n) makes a call to “fwconsole extip” and bombs out the entire install after the timeout. fwconsole extip is trying to access http://mirror.freepbx.org/whatsmyip.php. The https version of the URL works.
Grepping around and changing the source as appropriate for both issues gets things going, but ideally shouldn’t be necessary. sipsettings could continue without the extip, the npm stuff could fall back to no proxy. Both maybe with a warning.
Probably should file a report, but family is about to show up for Christmas gatherings for now.
is that the latest version of Commercial EPM on the mirror.freepbx.org is showing as 15.0.5. I’m currently running 15.0.24.28 which was downloaded from mirror1/mirror2.
It is currently showing newer versions of modules such as Asterisk SIP Settings (15.0.6.20) are available (have 15.0.6.19 installed) so it looks like most modules are OK. It’s just Commercial EPM hasn’t been updated. Do I need to raise a ticket somehow or can someone from Sangoma check that mirror.freepbx.org has all of the current modules and is being updated correctly?