[Resolved] Site key problem

[Author]

Posts

[francois]

We just moved our website from a dedicated server to AWS, I now have the message that says that there is a communication error with the Toolset servers. I found out that my site URL had changed, so I created a new site on my Toolset Account, unregistered my site and re-registered it and the message is still there.

I am also a WPML user, I did exactly the same for WPML and it removed the message immediately.

Thanks

[Shane]

Hi Francois,

Not sure why you are still getting these messages, did the site register successfully with the new keys ?

If not can you re-create them using the method below.
https://toolset.com/faq/how-to-install-and-register-toolset/#automatic-installation-once-you-have-types-plugin-installed

Please let me know the results and we can take it from there.

Thanks,
Shane

[francois]

I just de-registered the site and registered it again with a new key, the key seems do be valid, no error message while validating the key, but I still see the warning message at the top of the page as well as in the plugins page.

[Shane]

Hi Francois,

Can you allow me to have admin access to the site so that I can have a look ?

I've enabled the private fields for your next response.

Thanks,
Shane

[Shane]

Hi Francois,

Thank you for the login.

So you need to check your network security settings and allow communications to Toolset.com.

From what I can see the connection is perhaps being blocked by the server.

Thanks,
Shane

[francois]

I don't understand then why I have no problem with WPML which use the same mechanism for updates and communication with the servers. I tried desactivating Wordfence, my security and firewall plugin, but it didn't resolve the problem.

[Shane]

Hi Francois,

I did some other checks on the site and I see that your site is able to connect to Toolset.com

I was able to update your types plugin with no issues at all. Even able to re-register your site with a key I created. What i'm going to do now is to escalate this as an exception to see what our 2nd tier supporters can find.

Finally you will need to re-add your site key as I removed it to do a short test. The good thing is that your site is functioning as intended.

Please keep the credentials open.

Thanks,
Shane

[francois]

OK, I just re-entered my key, keep me informed of any solutions from your team. I am keeping the credentials open until I have further news on the issue so you can make more tests.

Thanks

[Shane]

Hi Francois,

So I was able to get some help on this one and managed to resolve the issue.

If you check on your backend you should no longer see the notice.

What I did was to go to wp-admin/update-core.php and hit check again. Once I did that the notice dissappeared.

Please let me know if this helps.
Thanks,
Shane

[francois]

All right Shane, thank you very much for your help.

[francois]

My issue is resolved now. Thank you!