Answers.Body: <p>It could be a timeout error related to Guzzle. By default the setting <code>http_timeout</code> is set to 5. You could try increasing that.</p>
  <p>I don't see where to set that setting in the UI, but you can do it using the API Explorer v4 (Support &gt; Developer &gt; API Explorer v4).</p>
  <p><strong>Reference</strong></p>
  <p>In the Civi codebase, that error message shows up in 2 places in <a href="https://github.com/civicrm/civicrm-core/blob/69259160e61163bd42b591c8795dfeafd9f7e80b/CRM/Extension/Browser.php#L225" rel="nofollow noreferrer"><code>/CRM/Extension/Browser.php</code></a>.</p>
  <p>There's a comment in code referencing an open issue raised by @JonGold 5 months ago about &quot;Extension directory times out when uncached.&quot; Maybe that's what you're experiencing.</p>
  <p><a href="https://lab.civicrm.org/infra/ops/-/issues/1009" rel="nofollow noreferrer">https://lab.civicrm.org/infra/ops/-/issues/1009</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-12T19:48:06.717Z
Answers.LastActivityDate: 2024-04-12T19:48:06.717Z
Answers.UserDisplayName: Justin657
Body: <p>We're getting this error on our updated 5.72.1 instance:</p>
  <pre><code>The CiviCRM public extensions directory at https://civicrm.org/extdir/ver=5.72.1|cms=Drupal could not be contacted - please check your webserver can make external HTTP requests
  </code></pre>
  <p>I looked this up on SE here and tried everything on the server end. I can wget that page from our server (gives me a list of xml file links). So I am guessing our server can make external requests. I have also flushed caches multiple times. I'm not sure what else this can be.</p>
  <p>Any pointers?</p>
  <p>It's unfortunate timing, as this annoying message comes up just as I'm trying to impress some folks on the features of CiviCRM and how powerful it can be with custom extensions :-).</p>
  
Tags: <error>
Title: The CiviCRM public extensions directory could not be contacted
ThreadText: # The CiviCRM public extensions directory could not be contacted
  
  (Asked by: username_0 on 2024-04-11)
  
  We're getting this error on our updated 5.72.1 instance:
  The CiviCRM public extensions directory at https://civicrm.org/extdir/ver=5.72.1|cms=Drupal could not be contacted - please check your webserver can make external HTTP requests
  
  I looked this up on SE here and tried everything on the server end. I can wget that page from our server (gives me a list of xml file links). So I am guessing our server can make external requests. I have also flushed caches multiple times. I'm not sure what else this can be.
  Any pointers?
  It's unfortunate timing, as this annoying message comes up just as I'm trying to impress some folks on the features of CiviCRM and how powerful it can be with custom extensions :-).
  
  **Tags:** error
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-04-12. Score: 0
  
  It could be a timeout error related to Guzzle. By default the setting `http_timeout` is set to 5. You could try increasing that.
  
  I don't see where to set that setting in the UI, but you can do it using the API Explorer v4 (Support > Developer > API Explorer v4).
  
  **Reference**
  
  In the Civi codebase, that error message shows up in 2 places in [`/CRM/Extension/Browser.php`](https://github.com/civicrm/civicrm-core/blob/69259160e61163bd42b591c8795dfeafd9f7e80b/CRM/Extension/Browser.php#L225).
  
  There's a comment in code referencing an open issue raised by @JonGold 5 months ago about "Extension directory times out when uncached." Maybe that's what you're experiencing.
  
  <https://lab.civicrm.org/infra/ops/-/issues/1009>
  
  
  ---
  
  