Can't update servers located in Philippines

Distro Discussion & Help
1

FreePBX Distro version 14.0.5.25

We have a number of FreePBX installs in a few different countries. All of them are able to use the update servers without issue except two of our servers in the Philippines (one of them connected via Globe Telecom, another via PLDT).

It feels like there there is some sort of country IP block on the update servers that would cause this, but I can’t imagine why this would be. Any workarounds? Setting up VPN just to update the servers seems a little silly.

[root@freepbx ~]# yum update
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
http://sng7.com/os/7.6/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://sng7.com/os/7.6/os/x86_64/repodata/repomd.xml: (28, ‘Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds’)
Trying other mirror.
sng-base | 3.6 kB 00:00:00
sng-epel | 4.7 kB 00:00:00
sng-extras | 3.4 kB 00:00:00
sng-pkgs | 3.4 kB 00:00:00
sng-updates | 3.4 kB 00:00:00
sng-pkgs/7/x86_64/primary_db FAILED
http://sng7.com/sng7/sng7/repodata/22f98df83a54971bab9363a0b4fd4936e841f2ceb1e3852a297f2038beead7b6-primary.sqlite.bz2: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.
sng-base/7/x86_64/primary_db FAILED
http://sng7.com/os/7.6/os/x86_64/repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.
sng-base/7/x86_64/group_gz FAILED
http://sng7.com/os/7.6/os/x86_64/repodata/bc140c8149fc43a5248fccff0daeef38182e49f6fe75d9b46db1206dc25a6c1c-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.
sng-pkgs/7/x86_64/primary_db FAILED
http://sng7.com/sng7/sng7/repodata/22f98df83a54971bab9363a0b4fd4936e841f2ceb1e3852a297f2038beead7b6-primary.sqlite.bz2: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.
sng-base/7/x86_64/primary_db FAILED
http://sng7.com/os/7.6/os/x86_64/repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.
http://sng7.com/os/7.6/os/x86_64/repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2: [Errno 14] HTTP Error 522 - The requested URL returned error: 522 Origin Connection Time-out
Trying other mirror.

2

From a shell prompt on the problematic system, do you get a similar error doing
wget http://sng7.com/os/7.6/os/x86_64/repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2

If so, try
wget https://sng7.com/os/7.6/os/x86_64/repodata/6614b3605d961a4aaec45d74ac4e5e713e517debb3ee454a1c91097955780697-primary.sqlite.bz2

If that doesn’t fail, my guess is that the ISP may be using a caching proxy for HTTP that is somehow corrupting the request. Try editing the .repo file to use HTTPS instead.

Another possibility short of a VPN may be a proxy server. You could set that up in the yum.conf file, so it doesn’t affect any normal operations.
https://docs.fedoraproject.org/en-US/Fedora_Core/3/html/Software_Management_Guide/sn-yum-proxy-server.html

3

Thanks for the response Stewart1 - yes, both wget commands (with and without https) give the same result:
ERROR 522: Origin Connection Time-out.

I’ll look into the proxy solution next…

4

Ah, weirdness. The command works fine from a different machine on the same network (Ubuntu machine). Now I’m wondering about network config issues (DNS?). Will report back…

5

Update: I found that we were piping these servers through our leased lines (which makes sense given their VOIP nature), but updates via the leased lines seems to fail for some reason. Once switched to DSL, the updates complete without issue.

It’s bizarre to me that this happens on both providers with their respective leased line products. Anyway, thanks for pointing me in the right direction!

6

https://freedomhouse.org/report/freedom-net/2018/philippines

Perhaps your a bad boy?

7

We’re still struggling with this issue - piping the servers through the leased lines is hit and miss (depends on provider and IP range).

Before I set up VPNs, is there anything else I can try?

None of the other distros / software we use have any issues like this, so it does feel like it might be actively be being geo blocked by FreePBX / Sangoma - is there a policy on this? We’ve spent thousands on commercial modules, so I feel like we should be able to access update servers without getting the runaround.

dicko: you’re / your

8

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