Https://mirror.freepbx.org is not working

Hi Guys

I’m trying to run updates on my FreePBX install and I’m seeing the following error in the GUI

Warning: Error retrieving updates from online repository(s) (https://mirror.freepbx.org). Online modules are not available.

From the command line I’ve tried this.

fwconsole setting MODULE_REPO https://mirror.freepbx.org
Changing "MODULE_REPO" from [https://mirror.freepbx.org] to [https://mirror.freepbx.org]

Then tried updating the module

fwconsole ma -R https://mirror.freepbx.org upgrade framework
Getting Remote Repo list...Done
No such repo: [https://mirror.freepbx.org], skipping
No repos specified, using: [commercial,standard,extended] from last GUI settings

Starting framework download..
The following error(s) occured:
 - Retrieved Module XML Was Empty

Any other suggestions? I can’t seem to get the updates working.

BTW I can ping that domain.

ping mirror.freepbx.org
PING mirror.freepbx.org (199.102.239.8) 56(84) bytes of data.
64 bytes from 199.102.239.8: icmp_seq=1 ttl=55 time=27.2 ms
64 bytes from 199.102.239.8: icmp_seq=2 ttl=55 time=25.0 ms
64 bytes from 199.102.239.8: icmp_seq=3 ttl=55 time=25.1 ms

The -R flag is not for setting a mirror server. It’s for declaring the repo. A repo is a single word like “commercial” or “standard”. Think of it like a label or group. You told the system to look for all modules labeled “https://mirror.freepbx.org”. Of course there are none because you’d need to use a valid word there [standard,extended,commercial]. You can’t change the mirror server on the fly like that and setting the repo flag is only useful if you only want to say install all commercial modules. Or all standard modules or all extended modules. Etc.

The command you want to run is:

fwconsole ma upgrade framework

Thanks for the clarification just tried that and got the following result.

fwconsole ma upgrade framework
No repos specified, using: [commercial,standard,extended] from last GUI settings

Starting framework download..
The following error(s) occured:
 - Retrieved Module XML Was Empty

Any other ideas?

I should be a little more clear.

I’m seeing this on my Dashboard.

framework (Cur v. 13.0.197.14) should be upgraded to v. 13.0.197.21 to fix security issues: SEC-2019-000

So all I’m trying to do is update it but the GUI updater is failing with this error.

Warning: Error retrieving updates from online repository(s) (https://mirror.freepbx.org). Online modules are not available.

Interesting, when I run this

fwconsole ma list

I can see this version in the list, I’m assuming this is the latest version of that module but my Dashboard thinks it’s not installed.

| framework | 13.0.197.21 | Enabled | GPLv2+ |

Are you sure the new mirror supports FreePBX 13? This post from @tm1000 says maybe it doesn’t… Cannot Connect to Online Repository (mirror1.freepbx.org, mirror2.freepbx.org)

Do things start working again if you put the mirror settings back the way they were?

fwconsole setting MODULE_REPO http://mirror1.freepbx.org,http://mirror2.freepbx.org
1 Like

Just ran this

fwconsole setting MODULE_REPO http://mirror1.freepbx.org,http://mirror2.freepbx.org

Then this

fwconsole ma showupgrades

But it seems to be failing. Not sure what log file to check.

fwconsole ma showupgrades
No repos specified, using: [commercial,standard,extended] from last GUI settings


                                                                          
  [Exception]                                                             
  Unable to Parse XML response from Mirror. See the log for more details  
                                                                          

ma [-f|--force] [-d|--debug] [--edge] [--color] [--skipchown] [-e|--autoenable] [--skipdisabled] [--snapshot SNAPSHOT] [--format FORMAT] [-R|--repo REPO] [-t|--tag TAG] [--] [<args>]...

When I try to check for updates at the GUI I see this.

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

I’ve just tried to check for updates on my FreePBX 15 system that is currently using mirror 1 & 2. I get the same error as you. I suspect they are down again. If I change to mirror.freepbx.org then a check for module updates succeeds.

I don’t know for sure but I suspect that mirror.freepbx.org doesn’t support FreePBX 13 that’s why you aren’t seeing any modules when you check there.

Try with mirror1 and 2 later and see if you have any luck. I expect that one of the Sangoma people will kick the servers in the morning USA time.

I have a brand new install (yesterday) hosted at Cyberlink that’s running 14 on which module updates do not work. Initially it was configured to use mirror1 and mirror2. It was returning:

I updated it to use mirror.freepbx.org and now it just doesn’t see any modules online.

I have about 8 other installs, mostly Freepbx 13 and they are throwing a “Cannot connect to online repository” as well. Last night I was getting the Whoops screen indicating it could not parse the XML response. The whole time https://status.sangoma.com shows everything is “operational”. :expressionless:

I have the same problem.

1 Like

Seeing the same issue with a new FreePBX14 install and running fwconsole ma upgradeall

Unable to Parse XML response from Mirror. See the log for more details

Something odd must be up. Now every server I have checked (FreePBX14) is not able to upgrade modules.

Had this issue across several installations yesterday, and continues today. Yesterday it would sometimes work, and sometimes fail. I had to keep running ‘fwconsole ma upgradeall’ over and over to get it to complete. Guess I picked the worst day to update!

1 Like

Monday (I think) one of the Sangoma guys mentioned that they are working on fixing a problem with their servers going unreachable and that they’d let us know when they got it fixed.

1 Like

I’m having same issue with Freepbx 13 and 14

1 Like

Any way you guys can try again?

I think we’ve got the mirror servers in a better spot now, but it would be good to know if there are any outstanding issues.

Thanks!
Matt

I was able to run an update successfully

It’s working now on both v14 and v13 deployments. Thanks!

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