[Resolved] Unable to register: Site key not matching
This thread is resolved. Here is a description of the problem and solution.
Problem:
I am having this issue where WPML does not seem to recognize the license key. Additionally, I can't find the configuration option to set the automatic translation mode or translate the page. This issue may be related to the key.
Solution:
To resolve the issue with the license key and access the WPML settings:
Hi, it looks like wpml does not recognize the key. This website was translated some time ago, but we are trying to work now with a new license, is it possible?
Also, I can’t see the configuration option to set the automatic translation mode. Also, I can't translate the page. Maybe all of this is because of the key.
Can you please go to your site's backend > Plugins > Add new > Commercial > and make sure that WPML is registered with the WPML key? If WPML is not registered, can you please click on "register WPML" and try to register WPML with the key from the initial page I mentioned?
Hello, on our website, too, the update daoes not work, resp. requires a (manual) site key entry. After entering the correct site key I get the error message:
"Connection error: Unable to get data from service. Detailed error: cURL error 60: SSL: no alternative certificate subject name matches target host name 'api.wpml.org'"
In order to register WPML, you need to generate a site key here (https://wpml.org/account/sites) and then copy and paste that site key in your site's backend by going to the Plugins tab on the left side vertical menu, then go to "Add new", then select the "Commercial" tab, and that's the area where you can add the WPML key.
If your domain name is "hidden link", then you should find the page I'm referring to here: hidden link
So can I understand that this error ("Unable to register: Site key not matching") is not showing up anymore?
Is that accurate? If that error is not showing up anymore, can you please mark this ticket as resolved?
Per our Support Policy, we can handle only one issue per ticket.
Continuing with one issue per ticket helps not only supporters to focus on one issue at once, but also enables other users to find solutions to their questions faster.