Access to wordpress.org failing

Wow…somehow I lost a lengthy response to this….
I did take option 2 from above and ran this script:

<?php
// Initialize cURL session
$ch = curl_init();

// Set cURL options
curl_setopt($ch, CURLOPT_URL, "https://wordpress.org");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); // Return the response as a string
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true); // Follow redirects, if any
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true); // Verify SSL certificate

// Optional: Set a user agent
curl_setopt($ch, CURLOPT_USERAGENT, "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36");

// Execute the cURL request
$response = curl_exec($ch);

// Check for errors
if (curl_errno($ch)) {
echo "cURL Error: " . curl_error($ch);
} else {
// Print the response
echo "Response from WordPress.org:\n";
echo $response;
}

// Close the cURL session
curl_close($ch);

It returned content so I don’t think firewall is an issue. I went back and retraced my steps. The timeout is set to 300 seconds, which by my calculations is 300,000 milliseconds which is why I wonder that the WordPress Events and News widget has this: RSS Error: WP HTTP Error: cURL error 28: Resolving timed out after 10030 milliseconds. Is there some other cURL setting somewhere?….

Clicking on the “Updates” and waiting for 300+2 seconds before it times out reveals this:
Secure Connection Failed. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Which is again strange, because the domain is secured by a wildcard certificate and other WP pages will display just fine. It’s the wp-admin functions that seem to have issues. The error on checking for updates occurs on the /wp-admin/update-core.php file which should be OK. The Apache directives don’t explicitly allow access to the wp-admin folder but that shouldn’t be necessary since it is a subfolder of the wp folder that is explicitly allowed with a “Require all granted” directive.

Still digging but reall.y appreciate your response

• This reply was modified 1 year, 3 months ago by petehelgren.
• This reply was modified 1 year, 3 months ago by petehelgren.

Once again, Thanks! So, what I am trying to wrap my head around is that the script I posted contacted the https://wordpress.org site successfully using SSL, so what change to the SSL libraries would be needed to have a successful connection? If I can connect to https://wordpress.org, what would I need to test differently to access https://api.wordpress.org? Seems like if I connect with SSL to using PHP cURL to https://wordpress.org, that confirms that SSL is correctly configured (or maybe not?).

Circling all the way back, this problem started with a relocation of the server and a change to the network infrastructure. Nothing on the server changed when my WP sites stopped accessing the https://wordpress.org site. Yes, that seems to point to a networks issue. The only “network” issue I can determine right now is that I have this issue in “Site Health” dashboard:

Your site is unable to reach WordPress.org at 198.143.164.251, and returned the error: cURL error 28: Resolving timed out after 10009 milliseconds, which is confusing in that the timeout in the wp-config.php file is 300 seconds. Maybe if I solved the timeout by extending it, that would fix the issue. I thought changing the wp-config.php file would extend the timeout, but even that didn’t seem to fix the 10004 millisecond timeout….

Again, thanks for all the assistence.