Pro licence validation failing with HTTP 503

Support
#1

Hi Themeco Support,

I’m currently unable to validate my Pro licence on:

When I attempt validation, WordPress is successfully reaching the Themeco validation endpoint, but the API is returning:

HTTP 503 Service Unavailable

The request is reaching:

https://theme.co/api-v2/validate/...

The response headers include:

Server: cloudflare
X-Powered-By: Express

The WordPress diagnostic output shows that the request is being sent successfully and a response is being received from Themeco, so this does not appear to be a local DNS, SSL, cURL or outbound connection issue on the hosting server.

The relevant response is:

[code] => 503
[message] => Service Unavailable

Could you please check whether there is currently an issue with the licence validation API, or whether there is anything specific affecting validation for this site?

I can provide the full diagnostic output privately if required.

Best wishes,

Scot

#2

Hello Scot,

Thanks for writing to us.

It may be caused by a plugin conflict, caching issue, or a browser extension preventing the site from validating correctly. I recommend following our troubleshooting guide to help identify and resolve the issue. If you haven’t seen our doc for license validation, please have a look at it.


Please share your details in a secure note. Please provide the following details

  • WordPress Login URL
  • Admin-level username and password

You can find the Secure Note button at the bottom of your posts

secure-note
secure-note1040×250 15.3 KB

Thanks

#3

Thank you, I had already cleared caches but tried again on your advice

This site has cloudflare, and cloudways caches, both cleared and now works

On another note, what is the best way to maintain licence status when doing staging-live push pulls?

#4

Hello Scot,

Glad to hear that clearing the Cloudflare and Cloudways caches resolved the issue. Regarding staging-to-live push/pull operations, the best approach is to maintain the live site as the primary validated domain and add the staging environment as the development/staging domain under the same license. Since our license code provides support for the staging server as well, you also need to register the staging server domain in the same license code.

Hope it helps
Thanks

#5

Thank you for your suggestion, I am on the lifetime unlimited Pro licence so one licence to rule them all.

I have used the same in both the staging and live but in doing the push-pull (Cloudways), the licence always seems to get left behind

#6

Hello Scot,

It looks like the issue may be related to aggressive caching, particularly because the validation information did not transfer correctly from the staging environment to the production domain. I would suggest purging all caches before performing the push to the live site.

Thanks

1 Like
#7

I’ll try that on the next run, thanks

#8

You are most welcome, Scot

1 Like