Hey @EarlySigns,
The issue you described is not happening in our sites so this is most probably an isolated case. There’s possibly an issue with your web host connection to our server.
Here are the most common causes for this and how to resolve them:
1. Server Firewall or Security Rules Blocking Outbound Requests
Many hosting providers block outbound cURL connections to external APIs for security reasons, or use Web Application Firewalls (like ModSecurity) that block requests to Themeco’s update API.
-
Solution: Contact your web hosting support team and ask if they are blocking outbound connections to
theme.co. Specifically, ask them to whitelist outbound traffic to https://theme.co on ports 80 and 443.
2. Check for Connection Errors via WordPress Site Health
WordPress has a built-in diagnostics tool that will tell you if the server is experiencing cURL or SSL issues.
-
Solution: Navigate to Tools > Site Health in your WordPress dashboard. Look under the Status tab for errors such as:
- “The REST API encountered an error”
- “Your site could not complete a loopback request”
-
“cURL error 60: SSL certificate problem” or “cURL error 28: Connection timed out”
If you see these, it confirms a server-side SSL/cURL issue that your host needs to address.
3. Server-Side Caching of Failed/Empty Requests
If the server attempted to fetch the extensions list before the license was activated or while there was a temporary network glitch, the empty response may be cached in the database. The theme caches this check for up to 12 hours.
-
Solution: You can clear the cache and force a new check by:
- Revoking the license key in Pro > Validation.
- Clearing your host’s server-side cache (e.g., Varnish, Nginx helper, or hosting cache) and any WordPress caching plugins.
- Re-validating the license key to trigger a fresh request.
