Failed to update modules

FreePBX Applications / Modules
1

When trying to update the modules, the following error message is displayed

Warning: Cannot connect to online repository(s) (https://mirror.freepbx.org). Online modules are not available.

Warning: Cannot connect to online repository(s) (https://mirror.freepbx.org). Online modules are not available.

2

Check dns.

from a shell:

ping mirror.freepbx.org
3

@jfinstrom

The server responds to the ping test successfully, even switching the repository server the failure remains

4

firewall?

5

@dicko

I performed the validation with the same disabled, remaining the error

6

Your ‘validation’ ?

( ICMP is not enough.)

7

cURL error 7: Failed connect to 172.20.1.22:1080; Connection refused

The IP 172.20.1.22 refers to the server access IP

8

172.20.1.22 is a non-routable ip address. so it must have been provisioned by you internally

9

@dicko
is an ip of the local network, applied to the server

Can you suggest any other tests?..pasosu por something similar

10

Well. you need your name service(s) to resolve the repo url (mirror.freepbx.org) to an actual internet address (104.22.48.127) before sending it to the inner-tubes.

(Have you been ‘gefingerpockering’ in any way with your network setup ?)

11

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

Module(s) requiring upgrades: allowlist, api, blacklist, bulkhandler, callrecording, contactmanager, core, endpoint, fax, firewall, framework, logfiles, oracle_connector, pms, restapps, sangomartapi, sipstation, sms, ucp, userman, vega, voicemail, voipinnovations
Upgrading module ‘framework’ from 15.0.17.63 to 15.0.17.64
Downloading module ‘framework’
Processing framework
Verifying local module download…Redownloading

In cURL.php line 443:

cURL error 7: Failed connect to 172.20.1.22:1080; Connection refused

12

For a better detail, follow the error via the server console

13

Until you fix where 172.20.1.22:1080 forwards your connections , you will continue to experience that.

14

This is going to be basic connectivity testing…
DNS, Routing, etc.

Your outputs show you are routing to a proxy or something on your internal network and that is where you are falling flat.

1 Like
15

Thank you all, I will be revalidating my internal network

16

Problem solved, proxy option, was active on the server, again, thank you all for the support

17

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