This is the error I am seeing:
Toolset needs to connect to its server to check for new releases and security updates. Something in the network or security settings is preventing this. Please allow outgoing communication to toolset.com to remove this notice.
Need help?
See the communication error details and let us know in Toolset technical support.
The communication error details are:
toolset: Connection error: Unable to get data from service. Detailed error: cURL error 28: Failed to connect to api.toolset.com port 443 after 8751 ms: Couldn't connect to server
Hi there
Sometimes a site is blocked by our firewall because some rule has been triggered, but I have checked your site and it is not blocked.
Which means either there is a temporary communication problem between your server and ours, in which case you can try again later and see if it works, or there may be restrictions on your server from contacting toolset.com, in which case you would need to check with your server admins to understand why.
Hi - I have been in touch with our host and they are still not sure what's going on. They double checked the firewall also and we cannot find what is causing the issue. Do you have other suggestions?
My host is now asking: Is it possible to get an IP range from Toolset?
Hello there,
Please check if the following addresses are added to the allow list and if the names are resolving to their respective IPs in the server:
toolset.com - [108.158.186.3]
api.toolset.com - [52.20.215.91]
d7j863fr5jhrr.cloudfront.net - [13.33.123.116]
Also, please check if the curl lib is up-to-date and if not, please check if by updating it the issue is fixed.
Hi. I was in touch with our host and they said that the firewall is not blocking and the server is not timing out. They said they are pretty sure it's an issue with the plugin. Do you have anything else we can look into to see why this is happening?
Hello,
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
**IMPORTANT**
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: enlace oculto
Please, let me know if you need any additional details. Have a nice day.
Hello there,
Thank you for sharing those screenshots.
I created a ticket internally to have our systems team checking if we might be blocking the connection attempts by chance.
I'll let you know as soon as I hear back from them.
Thank you,
Mateus
All right,
Our team checked it thoroughly in our servers, they looked at logs and they couldn't find any blocked requests coming from your website or site's IP.
There's something in the server or Firewall that is preventing the curl request on our addresses, eg.: api.toolset.com.
I'm afraid you'll need to follow up with the hosting/firewall support team so they double-check what can be causing this issue.
You might want to try to temporarily disable the firewall and test it again. Then you can reactivate it quickly afterwards.
But based on our tests there's something preventing that request to be done on the server or site's side that needs to be addressed.
Ok thank you for looking. We already tried deactivating the firewall and they tested it again and the error was still there. I'll reach out to them again.