I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
Also, please update all WPML plugins to the latest version in WP > Plugins > Add new > Commercial Tab.
Thanks for your reply. I can see the issue here hidden link . it says your sitekey does not match your domain name.
Please go to your account dashboard here https://wpml.org/account/sites/ and register a new sitekey for your domain. Then, replace the sitekey in WP > Plugins > Add New > Commercial Tab.
Thanks for your patience. Please go through the feedback from our 2nd Tier Support below.
We've been investigating why the WPML-related functionality isn't working correctly on your staging site, and it looks like the issue centers around the REST API requests being redirected unexpectedly.
Here’s a summary of what we found:
- A request to one of the WPML REST endpoints (/wp-json/wpml/tm/v1/ams/register_manager/) returns a 302 redirect to itself, which likely causes a loop and prevents proper execution.
- Other REST API calls, such as the one made when clicking "Check for Updates" on the WPML plugin, are also being affected. For example, the request to /wp-json/wpml/v1/updates is being redirected (301) to a version with a trailing slash (/updates/), which results in a 404 Not Found error.
- We suspect this is due to a combination of:
- The site being behind Cloudflare, and
- Custom redirect rules in the .htaccess file or server-level configuration, which may be interfering with how REST requests are handled.
To rule out the obvious, we temporarily replaced the custom .htaccess and wp-config.php files with standard versions, but the issue persisted — which suggests that these customizations may not be the direct cause.
There is also a Kinsta MU-plugin in place, which might be playing a role, though we haven’t confirmed that.
### Recommendation:
At this point, we suggest contacting Kinsta support to review how the server is handling REST API requests — particularly in relation to redirects, Cloudflare, and REST route rewrites — since the issue appears to be rooted in the server environment rather than WPML itself.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
