Registering site, Code 0: cURL error 28

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are trying to register your site using WPML and encountered a cURL error 28.
Solution:
First, ensure that SELinux is disabled, as its status will not impact the httpd_can_network_connect setting. Next, to diagnose the issue further, attempt to connect to a third-party host using custom code. You can use the

wp_remote_get

function as shown below:

/** @var array|WP_Error $response */<br />$response = wp_remote_get( 'http://www.example.com/index.html' );<br /><br />if ( is_array( $response ) && ! is_wp_error( $response ) ) {<br />  $headers = $response['headers']; // array of http header lines<br />  $body    = $response['body']; // use the content<br />  var_dump($headers); //output the headers<br />  var_dump($body); //output the body<br />}

This test will help determine if the issue is specific to our domains or a broader problem affecting all domains.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: ATE

This topic contains 0 replies, has 0 voices.

Last updated by Lauren 3 weeks, 3 days ago.

Assisted by: Lauren.

Author	Posts
January 8, 2025 at 3:59 pm #16574310
kappnerC	Background of the issue: I am trying to register my site using WPML. The issue can be seen at the following link: hidden link Symptoms: I encountered an error with code 0: cURL error 28. Questions: How can I resolve the cURL error 28 when registering my site?
January 8, 2025 at 5:58 pm #16574916
kappnerC	Please send updates to: barrygirsh@gmail.com
January 9, 2025 at 7:20 pm #16579554
kappnerC	Need to resolve this issue, we're having the same problem with another site on this server, discovermandarina.com. Thank you
January 10, 2025 at 6:08 pm #16582883
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	I'm unable to send responses to an additional email, the responses will go to the email address on file in your wpml.org account. Please try the following steps: 1. unregister your site from WPML and then register it again. - Unregister: https://wpml.org/faq/install-wpml/#unregister - Register: https://wpml.org/faq/install-wpml/#register 2.Check the Installer Log under WPML > Support to ensure the subscription was working correctly. 3. Go to Plugins -> Add New -> Commercial and click 'Check for Updates' to see if any messages appeared. Do you have any messages? If so, let us know. 4. Check with your hosting provider to ensure that specific IPs crucial for WPML's functionality are resolving correctly. I know they checked the URLs, but please also have them confirm the IPs. The IPs to check are: d7j863fr5jhrr.cloudfront.net: 13.33.123.118 cdn.wpml.org: 52.85.213.119 api.wpml.org: 54.221.250.24 api.toolset.com: 34.193.222.18 If these are not resolving, your hosting provider may need to manually add these IPs to the /etc/hosts file. 5. COnfirm that your hosting provider has the WordPress REST API enabled. Please let me know the results after following these steps.
January 11, 2025 at 12:31 pm #16583892
kappnerC	Unregisted site, not able to connect. 'X' next to bothe WPML API server and Toolset API server 3. Go to Plugins -> Add New -> Commercial and click 'Check for Updates' to see if any messages appeared. Do you have any messages? If so, let us know. Connection error: Unable to get data from service. Detailed error: cURL error 28: Failed to connect to api.wpml.org port 443: Connection timed out I added these IPs to our firewall and still not able to connect to your server Please have your support team look into this to see why we are not able to resolve this ASAP! We can not wait. Thank you!
January 11, 2025 at 1:39 pm #16584002
kappnerC	does httpd_can_network_connect need to be enabled?
January 13, 2025 at 7:44 pm #16590532
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	Yes, please make sure this is enabled. Please see the section in yellow at the top of this page: https://wpml.org/forums/topic/your-site-cant-communicate-with-https-api-wpml-org/
January 14, 2025 at 8:27 pm #16594838
kappnerC	Just spoke with GD support and this is what they were able to figure out... 1. not able to ping or curl api.wpml.org (able to curl and ping from the server no problem) 2. times out at aws 3. problem on aws or wpml I need to get this resolved ASAP!
January 15, 2025 at 6:36 pm #16598886
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	Thanks for the update, I'm asking our second tier support to take a look and see what else we can test from our end.
January 16, 2025 at 3:07 pm #16602589
kappnerC	Can you please expedite this, this ticket has been on hold over a week now and I am convinced our sites are blocked by your firewall. Thank you
January 16, 2025 at 3:24 pm #16602742
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	I escalated this to our second tier support and this is what they found. The error 28 means timeout, so it might be that the server of the user has forbidden to make outbound requests - thus cannot connect to our authentication servers. Even if the ping is not working, the hosting should be able to do a curl request There is a image attached of a sample of what he means. Also there was a way to check for if a site is blocked in our firewall in MatterMost via the /firewall command and the hostname. I have attached a second image of what we have got there. In the image you can see we searched for "mayakoba.com" but the domain listed here is not the same as you can see (similar-ish but not the same) so, our second tier thinks the site is being blocked BEFORE it reaches our firewalls. Please share this with your hosting provider or whoever manages the server settings and hopefully we can get to the bottom of why it is being blocked.
January 21, 2025 at 5:42 pm #16620072
kappnerC	Attaching curl and traceroute screenshots initiated from our server. The curl request simply hangs, does not respond. The traceroute shows a stop at 99.82.180.188 (99.82.180.188) which I assumed was on your end. Is this your server or a stop inside your firewall?
January 21, 2025 at 6:10 pm #16620159
kappnerC	Server hostname: 142.176.169.192.host.secureserver.net
January 21, 2025 at 6:22 pm #16620164
kappnerC	Our server primary ip is 192.169.176.142. Can you confirm these are not being blocked?
January 21, 2025 at 6:47 pm #16620193
kappnerC	From GD support...I want to confirm there was no issues with the Godaddy server as we have checked and found it is working completely fine and the issue was with WPLM server outside of Godaddy.