Most WordPress sites connect to Siteligent without any issues. When a connection doesn't work or a previously connected site becomes disconnected, the cause is usually related to the Siteligent Connector, SSL, a firewall, Cloudflare, or another security tool blocking the connection.
This guide covers the most common connection problems and what you can check to resolve them.
Connection Stays on "Pending"
If a newly added website remains in Pending, the connection between your WordPress site and Siteligent hasn't been completed yet.
What to check
Log in to your WordPress admin dashboard.
Go to Plugins and make sure Siteligent Connector is installed and active.
Open Settings → Siteligent.
Check that you've entered the connection token generated for this website.
Click Connect.
Return to your Siteligent dashboard and check the site's status again.
If you waited too long before using the connection token, it may have expired. Generate a new token from Siteligent and try the connection again.
"Invalid Token" Error
A connection token is temporary. If the token has expired or you're using an older token, Siteligent won't be able to complete the connection.
How to fix it
Return to your Siteligent dashboard.
Open the pending site.
Generate or regenerate a new connection token.
Copy the new token.
In WordPress, go to Settings → Siteligent.
Replace the old token with the new one.
Click Connect.
Try to complete the connection soon after generating the new token.
"SSL Error" or Certificate Warning
Siteligent requires a secure HTTPS connection to your website. If your SSL certificate is expired, invalid, self-signed, or otherwise not trusted, the connection may be rejected.
How to fix it
Check that:
Your website loads correctly using
https://.Your SSL certificate is valid and has not expired.
The certificate is trusted by standard browsers.
Your domain is correctly configured on your hosting server.
If you've recently renewed or replaced your SSL certificate, allow some time for the change to take effect before trying the connection again.
"Connection Refused" or Authentication Error
Your website may be protected by an additional authentication layer that prevents Siteligent from reaching it.
This can happen with:
Staging environments
Development sites
HTTP Basic Authentication
IP restrictions
Hosting-level access controls
How to fix it
Check whether your website requires a username and password before the site can be accessed.
If your staging or development environment restricts access by IP address, make sure the required Siteligent IP addresses are allowed by your hosting or firewall configuration.
Site Suddenly Shows as "Disconnected"
If a site was previously connected but now shows Disconnected, something may have changed on the website or server.
Common causes include:
The Siteligent Connector was deactivated or removed.
A firewall started blocking Siteligent requests.
Cloudflare or another CDN is blocking requests.
A WordPress security plugin is blocking the Connector.
Your server is temporarily unavailable.
Server or security settings were recently changed.
Step 1: Check the Siteligent Connector
Log in to WordPress and go to Plugins.
Make sure Siteligent Connector is installed and active.
If it was deactivated, activate it and then return to Siteligent
Step 2: Check Your Security Plugin
If you're using a security plugin such as Wordfence, Sucuri, or another firewall/security solution, check its activity or block logs.
Look for requests that were blocked around the time the connection stopped working.
Step 3: Check Cloudflare or Your Firewall
If your website uses Cloudflare or a server-level firewall, check whether recent security rules are blocking Siteligent.
You may need to allow the required Siteligent IP addresses and user agents.
Step 4: Sync the Site
After making changes, return to Siteligent and manually sync the website to check its connection again.
If the site still shows as disconnected, continue troubleshooting your firewall and security configuration.
Connection Works but Some Features Don't
If your site shows as Connected but a particular feature isn't working, the issue may not be with the connection itself.
For example, a firewall or security plugin could allow the initial connection while blocking specific requests later.
In this situation:
Check your WordPress security plugin logs.
Check your Cloudflare or firewall events.
Look for requests from Siteligent that have been blocked.
Make sure the required Siteligent IP addresses and user agents are allowed.
Try the operation again.
Still Having Problems?
If you've checked the Connector, SSL, firewall, and security settings and the site still won't connect, contact Siteligent Support.
When contacting support, include:
The affected website
The connection status shown in Siteligent
Any error message you're seeing
Whether the site has Cloudflare or another firewall enabled
Any recent changes to your hosting, SSL, or security configuration
This information can help the support team identify the problem more quickly.