KNOWN ISSUES
There are a few known issues when you cannot connect the WordPress plugin to your user profile. See the info below on how to fix this.
1. Please check if any of these known issues apply to your case:
- Old PHP versions below 7.2 might trigger a fatal error for the plugin
- WP version minimum 5.9
- Cloudflare CDN is blocking the connection because of caching
- Have you deactivated your caching plugins?
- Does this error still exist if you temporarily disable all other plugins? If not, then one of the plugins is funking this up.
2. You cannot reconnect after Plugin reinstallation
Have you installed and reinstalled the plugin, and now it is not connecting anymore? Please ask our support to revoke your API token.
3. Web Hosting Providers that block the server connection by default
Some hosting providers have been found to set an unnecessarily high level of restrictions in favor of “Security.” In this case, you need to contact their support team and ask them to lower their restrictions. If they do not comply, the ViSPR plugin will only work after a website migration to another hosting provider.
- Namecheap
- Rootpal
- Strato
- A2 hosting
We recommend Siteground, as we are hosting with them and know that they are one of the very best hosting providers on the planet. Siteground is so dedicated to WordPress that they even develop their own plugins to optimize WordPress for their server settings.
4. Hosting Server Config Problems related to timeout (cURL)
When you get an error “cURL error 28: Connection timed out after 5000 milliseconds“, this is a problem with your hosting server configuration, not the ViSPR plugin.
Here are two sites that show you how to fix this. Whichever works best for you:
If you need help with that, please ask your developer or hosting provider.
5. What to do if nothing works?
If nothing works, please consider giving our developer temporary admin access to your WordPress so we can try to fix this for you. That will help us learn more about this issue, and we might be able to spot a nasty bug that we can fix for everyone else 🙂