If you see an error message saying that WPML is unable to connect to WPML.org, it is because of an issue from the server or your internet connection. Here are some troubleshooting tips to get you back on track.
Force Another Check
This is often a temporary issue. You can force another check to clear the notice by going to Dashboard → Updates and clicking the Check again button.
Check the Installer Support Log
If this does not work, check the error log by going to WPML → Support and clicking Installer Support.
Here is a summary of what the following errors mean and any action you can take:
Log error message | What it means | What you can do |
---|---|---|
wpml: cURL error 6: Could not resolve host: api.wpml.org | You (if testing from a local development install) or your host are not connected to the internet or its DNS server is not properly configured or reachable. | Check your internet connection or contact your hosting support and try again |
wpml: cURL error 60: SSL certificate problem: self signed certificate | WPML.org is incorrectly pointed to 120.0.0.1, the IP of the shared server, or to another third-party IP, and the SSL certificate isn’t trusted | Check that your site has a valid SSL certificate and is correctly pointed to WPML.org in the host file (if you don’t know what this is, contact your hosting provider for assistance) |
wpml: cURL error 7: Failed to connect to api.wpml.org port 443: Bad access | WPML is blocked by a firewall | Contact your hosting provider and ask them to whitelist the following domains:
|
wpml: cURL error 28: Operation timed out after 45009 milliseconds with 0 bytes received | There was a temporary slow-down between your server and WPML.org | Try again in a few minutes. If the issue persists, ask for assistance from your hosting provider |
If you don’t see any errors in the log, click Check now next to Installer System Status.
Get Help From Our Support Team
If none of these solutions solve the issue, please open a ticket so our support team can investigate it further.