We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

An error occurred while connecting to the Provider

    • 22303 MODX Staff
    • 10,725 Posts
    opengeek Reply #21, 16 years, 1 month ago
    See http://modxcms.com/forums/index.php/topic,51831.0.html for another possible issue confirmed on another hosting provider.
      Jason Coward
      Chief Architect @ MODX
      http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
      • 21054
      • 78 Posts
      nclemente Reply #22, 16 years, 1 month ago
      I’ve figured out what was wrong (at least in my situation).

      If your host blocks outgoing connections allow the following:

      74.55.204.125 at port 80 at the host 7d.cc.374a.static.theplanet.com

      I found this out accidentally as I was investigating recently blocked connections.
        • 1061
        • 81 Posts
        alex_dutch Reply #23, 15 years, 6 months ago
        I’ve got the same problem.
        My hoster is blocking ext. connections.
        And I each time, then a new scripts need the ext. connections, send email.
        Please allow ext. conn. to some doamin, to hostmaster admin.
        And now a can’t install extras, only list of them.

        I get the errors:
        [2011-03-03 18:31:24] (ERROR @ /connectors/workspace/packages.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:31:24] (ERROR @ /connectors/workspace/packages.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:31:35] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:31:35] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:31:36] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:32:25] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 18:44:17] (ERROR @ /connectors/workspace/packages.php) Could not connect to provider at: http://rest.modxcms.com/extras/
[2011-03-03 20:00:07] (ERROR @ /connectors/workspace/packages-rest.php) MODx could not download the file. You must enable allow_url_fopen, cURL or fsockopen to use remote transport packaging.
[2011-03-03 20:00:07] (ERROR @ /connectors/workspace/packages-rest.php) Не могу скачать пакет в: http://modx.com/extras/download/?id=4d556c78b2b083396d000c21


        But thing is, they say that we configured yours account to allow ext. conn. to rest.modxcms.com(ip - 199.47.222.137).
        Now, i’ve can only get the list of extras, but can’t install.
        I’ve installed extras manualy.

        P.S. I’ve already have opened IP 74.55.204.125. And I recieve news on backend from rss.
          • 28215
          • 4,149 Posts
          splittingred Reply #24, 15 years, 6 months ago
          Change the provider url to http://rest.modx.com/extras/
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 1061
            • 81 Posts
            alex_dutch Reply #25, 15 years, 6 months ago
            The same...
            [2011-03-04 12:21:28] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modx.com/extras/
[2011-03-04 12:21:28] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modx.com/extras/
[2011-03-04 12:22:26] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modx.com/extras/


            Hostmaster admin allow ext.conn. to port 80, may be need other ports? (443)
              • 28215
              • 4,149 Posts
              splittingred Reply #26, 15 years, 6 months ago
              You definitely need to open up port 80, at the least, as well as any other ports used over cURL.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 1061
                • 81 Posts
                alex_dutch Reply #27, 15 years, 6 months ago
                80 port opened for defaults for ext.conn.
                What other ports should be opened?
                  • 34084 ☆ A M B ☆
                  • 756 Posts
                  CharlesMx Reply #28, 15 years, 2 months ago
                  for those wondering, I did a trace on request for rest.modx.com and all request are being made through TCP port 80.

                  Report sample:
                  tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
tcp        0      0 192.168.111.23:33766    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:33765    199.47.222.137:80       TIME_WAIT  
tcp        0      0 192.168.111.23:40455    199.47.216.148:80       ESTABLISHED
                    Evo Revo // Ubuntu, CentOS, Win // Apache 2x, Lighttp (Lighty)
                    Visit CharlesMx.com for latest news and status updates.