Host Wants Information on Why Its Not Validating

Since this thread was closed: Validation Not Working - After Entering Code - Nothing Happens

I am posting a new one.

Host is asking the following:

Our System Administration team has reviewed the issue and requires some additional information from the Cornerstone vendor to determine whether the hosting server is blocking the request.

Please provide the following details from the vendor:
• Their logs or troubleshooting findings confirming that the request is being blocked.
• The exact URL/API endpoint that Cornerstone is attempting to connect to.
• The error message or HTTP status code received.
• If available, the source IP and destination IP involved in the failed request.

Hey Haley,

Thank you — please pass the following to your host’s System Administration team.

Endpoint. Validation is a plain outbound HTTPS GET from your web server to:

https://theme.co/api-v2/validate/{purchase-code}/?product={product}&siteurl={your-site-url}

Updates use the same host: https://theme.co/api-v2/packages/{key}/

Both are GET requests issued through WordPress’s HTTP API, 15 second timeout, port 443. There is no callback to your server and no fixed source IP on our side — the request originates from your own web server’s address. Only outbound HTTPS to theme.co needs to be permitted.

Please also confirm: outbound requests to theme.co are allowed, cURL is enabled, allow_url_fopen is enabled, and CA root certificates are up to date. Outdated certificates cause the request to fail silently, which matches “nothing happens”.

Quick Check

  • Confirm PHP version is 8.1+.

  • Confirm Cornerstone is on the latest version.

Troubleshooting

  1. Get the exact error – append &x-verbose=1 to the URL of the validation screen and retry. This reveals the server-side error and status code your host has asked for. Please post what it returns.

  2. Test from the server – ask your host to run curl -v https://theme.co/api-v2/validate/ on the web server itself. This shows whether the request is refused, times out or completes, along with the addresses involved.

  3. Confirm the registered URL matches exactly – a difference in www or non-www, or http versus https, causes validation to fail even when the connection is fine.

Recommended Resources

Hope this helps.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.