Site Cannot Communicate with WPML API

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.

This topic contains 3 replies, has 2 voices.

Last updated by Andrey 1 year, 2 months ago.

Assisted by: Andrey.

Author	Posts
August 31, 2023 at 4:19 pm #14322449
patrickV-3	We're getting errors when trying to update the plugin and when trying to activate a license. I checked the Installer Support logs and we're seeing the following error: Your site can't communicate with hidden link. Code 403. I've looked through the troubleshooting steps and contacted Pantheon (the site host) about whitelisting the URLs and they told me that they do not block any URLs. This error is also occurring on other sites we have hosted on their platform. Looking at the Installer Support logs the error seems to have started happening around August 23rd.
September 1, 2023 at 8:20 am #14325007
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for contacting WPML support. Have you done any particular steps around this date? Installing or updating plugins, maybe anything else. To ensure we are on the same page, has your hosting provider confirmed that allow the following domains? – wpml.org – cdn.wpml.org – api.wpml.org – api.toolset.com – cloudfront.net https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
September 1, 2023 at 2:12 pm #14327213
patrickV-3	We made some changes to a PHP template on August 21st but other than that there has been no other changes to the site around that time. Yes, the host has confirmed to me that those domains are not being blocked by them.
September 4, 2023 at 7:58 pm #14339169
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thanks for the update. Could you please upload the screenshot of the issue?
September 5, 2023 at 1:57 pm #14345165
patrickV-3	Looks like whatever the issue was solved itself as everything is working without issues now.