Skip Navigation

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 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 -
- - - - - - -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 3 replies, has 3 voices.

Last updated by Waqas Bin Hasan 1 year, 6 months ago.

Assisted by: Waqas Bin Hasan.

Author Posts
July 5, 2023 at 7:56 pm #13953803

ianW-10

I am trying to: start translating the production site.

After changing from from dev to production the site shows as registered on WPML and on the site as well, but there is an error still showing the WPML can't contact the server. It is unable to connect the credits balance despite credits being assigned.
I have registered and unregistered the site repeatedly which works fine, I have enabed / disabled caching and security plugins, and also tried adding / removing the site key in wpconfig (which was enabled during dev).

Link to a page where the issue can be seen:
hidden link The tools page on the plugin shows an error connecting to automatic translation.

I expected to see:the ability to translate pages

Instead, I got: The tools page on the plugin shows an error connecting to automatic translation.

The server is a AWS lightsail standalone instance. hidden link
All server settings and health seem to match the requirements indicated in WPML and registration succeeds but the assignment of translation credits done on the WPML site does not.

WPML Error.jpg
WPML registered.jpg
WPML site key.jpg
July 5, 2023 at 11:41 pm #13954333

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

While waiting for one of my colleagues to help you, please review the following

Go to WPML->support->Advanced Translation Editor(ATE) -> Error logs -> do you see any errors listed there?

The warning you are getting is related to the ATE server rather your site key connection.

Also, verify that the IPs from the following domains are whitelisted

wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net

July 6, 2023 at 12:17 am #13954383

ianW-10

Thanks Bobby,

There is a repeating error that began when the site was moved from development to production and stopped when I reset the site key per the support docs.

In terms of whitelisting the domain names - is there a specific place in the plugin for this whitelisting? I don't see an obvious place in WPML to do so.

The error text pasted below.

Thanks,

Ian

The error text:
2023/07/04 8:57:53 PM
ATE Server Communication
WPML has detected a change in your site's URL. To continue translating your site, go to your WordPress Dashboard and tell WPML if your site has been moved or copied. 0 0 {"url":"https:\/\/ate.wpml.org\/api\/wpml\/languages\/mappings","requestArgs":{"method":"GET"},"status":426}

July 6, 2023 at 8:49 am #13956625

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting the support, I am assigned this ticket and 'll try my best to help you on the matter.

To whitelist those domains you'll need to contact your hosting provider, there's no option for this in WPML. Please also see https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/ for some relevant details and a few more checks.

Besides the above mentioned, please also try the followings, if whitelisting doesn't work:

Take a full backup of site and database before proceeding.

- Deactivate all other plugins except WPML's.
- Switch to a standard theme like 2021 or 2023.
- And see if it works?

If it works fine, then switch to your theme and recheck. And continue activating each plugin one by one while rechecking. This way we'll be able to find if there's any conflict with a plugin or theme.

Please let me know how it goes.

Regards.

The topic ‘[Closed] WPML unable to connect to WPML server credits after switch to production’ is closed to new replies.