Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Kyiv (GMT+03:00)

This topic contains 14 replies, has 0 voices.

Last updated by Andrey 1 day ago.

Assisted by: Andrey.

Author Posts
August 4, 2025 at 6:53 pm #17294505

jimmyJ-3

Background of the issue:
I am trying to register the WPML plugin on my site hidden link. I am using GoDaddy as a server provider and also using Cloudflare.

Symptoms:
I get a connection error when trying to activate the plugin: 'Connection error: Unable to get data from service. Detailed error: cURL error 28: Connection timed out after 10028 milliseconds.' I see a red 'X' on WPML API server and Toolset API server in the 'installer system status'.

Questions:
Where and how do I whitelist the domains wpml.org, cdn.wpml.org, api.wpml.org, api.toolset.com, and cloudfront.net?
Can you help me register this plugin on my site, maybe using the backend or another method?

August 4, 2025 at 7:25 pm #17294616

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for contacting WPML support.

It appears that your hosting provider may be blocking access to our API.

Please contact your hosting provider and ask them to whitelist the following domains:
• wpml.org
• cdn.wpml.org
• api.wpml.org
• api.toolset.com
• cloudfront.net

You can find more details in the following article:
https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/

August 4, 2025 at 8:16 pm #17294719

jimmyJ-3

I got this from my server-provider:

"Thank you for confirming. I have discussed this with our team, and unfortunately, we do not have the ability to whitelist external domains on shared hosting.

If you need that kind of ability you would need to switch to a VPS. On VPS you can control the traffic and firewall."

But you sure I need to whitelist these domains? Why is that? I have alot of plugins, and I have not had any issues like this before.

So I can not register now? or is there anything else we can do to register this plugin?
Let me know, thanks.

August 5, 2025 at 3:04 pm #17297080

jimmyJ-3

So... is it possible to register this plugin on my site at your end?

I need to know, so I can move on to the next plugin, if this isn't working.

Thanks.

August 5, 2025 at 3:18 pm #17297154

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

I’ve reviewed our firewall logs, and we’re not blocking your website. While it’s not strictly necessary to whitelist domains, I recommend checking with your hosting provider to determine why your site is unable to connect to the WPML API. Something on the server side is likely preventing the connection.

As a workaround, you can try registering WPML using a constant in your wp-config.php file:
1. First, retrieve your site key from your WPML account.
2. Then, add the following line to your wp-config.php file (replace YOUR_SITE_KEY with your actual key):

define('OTGS_INSTALLER_SITE_KEY_WPML', 'YOUR_SITE_KEY');

3. After saving the changes, go to your WordPress dashboard → Updates and click “Check again” to refresh the repository data.

More details:
https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/#how-can-i-force-another-check-when-wpml-cant-connect

Before doing so, I recommend temporarily deactivating all non-WPML plugins and switching to a default theme (if possible) to ensure that no third-party plugin or theme is interfering with the connection.

If the issue persists, please contact your hosting provider to investigate the server-side restriction further:
https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/

Let me know how it goes.

August 5, 2025 at 4:16 pm #17297355

jimmyJ-3

Ok thank you.

I’ve just attempted the setup, but I’m now seeing an “invalid key” message in my WordPress dashboard (see attached images).

I also deleted the site from my WPML account and re-added it to generate new keys.
Not sure if that may have caused the issue for an invalid key?

So, what would be the next step? Can you guys give me a valid key maybe?
Let me know, thanks.

pic.02.png
pic.01.png
August 5, 2025 at 5:17 pm #17297533

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

I suspect it is not a key issue, but rather that your firewall is blocking the connection.

While you see
I see a red 'X' on WPML API server and Toolset API server in the 'installer system status'
you most likely won't be able to register.

Can you please try the other steps I suggested and let me know how it goes?

August 6, 2025 at 9:51 am #17298993

jimmyJ-3

Ok thank you.

I've now paused Cloudflare for the domain, and it should take a few hours for the changes to fully propagate.
It's possible that Cloudflare's firewall was blocking your API connection, but we'll know more once I attempt to register the plugin again after the update.

I will also deactivate all plugins and change theme.

I will update you after this, thanks.

August 6, 2025 at 11:53 am #17299308

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

Please try registering your site using the standard method through the WordPress admin area, without using the constant in your wp-config.php file. Also, make sure to remove any existing site keys and generate a new one from your WPML.org account to ensure the key you are using is valid and up to date.

August 8, 2025 at 12:28 pm #17305378

jimmyJ-3

Got this from GoDaddy's support team:

Thank you for the detailed reply.

I reviewed your instructions and can confirm that the issue is server-related and connected to i360. I’ve just received an update from one of our engineers who investigated the hosting service. They identified that the problem isn’t due to IPs being directly blocked by i360, but rather relates to the version of the software in use.

A request has already been submitted to the Advanced Hosting Operations team to roll out the necessary update and perform further testing on the platform.

So we will see what happens after they update.
I'll let you know soon, thanks.

August 8, 2025 at 3:13 pm #17305828

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for sharing the details.

I hope the issue will be resolved soon and you’ll finally be able to register WPML.

August 13, 2025 at 3:07 pm #17318303

jimmyJ-3

I'm still waiting for GoDaddy's team to address the issue, I'm hoping for an update soon.

I'll get back to you as soon as I hear from them.
Thank you.

August 13, 2025 at 4:36 pm #17318594

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Sure. Thank you for keeping me updated.

August 16, 2025 at 9:02 am #17324652

jimmyJ-3

Hi again,

Unfortunately, the issue with registering the plugin still hasn't been resolved.
I'm wondering, would it be possible for you to fix this on your end somehow?

I reached out to another plugin developer who mentioned the following regarding MultilingualPress:

“MultilingualPress does not require any external API connection or license registration to work. The plugin runs entirely within your WordPress Multisite installation, so you won’t encounter timeouts or connection errors during activation or use.”

Given that, do you think there's a workaround or alternative method we could try to get this plugin registered successfully?

If there's no viable solution, I would unfortunately need to request a refund.
Please let me know how you'd like to proceed.
Thank you.

August 18, 2025 at 10:40 am #17327359

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

You mentioned the following:

They identified that the problem isn’t due to IPs being directly blocked by i360, but rather relates to the version of the software in use.

Unfortunately, since this is a server-side issue, we’re unable to resolve it from our end.

As a possible workaround, could you try activating WPML on an alternative hosting environment (where there are no blockers) or a local setup, and then copy your site back once it’s working?