Cannot renew free Basic license on 5.2.2 — register.elastic.co reCAPTCHA shows "Invalid site key"

Hi,

I'm trying to renew the free Basic license for a self-managed Elasticsearch/Kibana 5.2.2 cluster (X-Pack), which uses the one-year Basic license that has to be re-registered.

The official self-service page no longer works:

  • URL: Register | Elastic
  • The reCAPTCHA fails to load and shows: "ERROR for site owner: Invalid site key"
  • As a result, the form cannot be submitted and no license file is ever sent.

I've already ruled out my side — it happens in a clean incognito window with no extensions, and on a different network — so the reCAPTCHA site key configured on that page appears to be invalid/expired on the server side.

Questions:

  1. Is there a working way to obtain a Basic license file for 5.2.2 now that this registration page is broken?
  2. Is there a private channel (DM or email) where someone from Elastic could send the Basic license JSON, so I can register it via Kibana License Management / PUT _xpack/license?

Hi @gbl0915,

Welcome to the community! Is upgrading an option for you? Elasticsearch 5.2.2 is long past EOL with 8 and 9 those under current support. Furthermore in versions 6.3 and later, X-Pack is included with the default distributions of Elastic Stack, with all free features enabled by default.

Let us know!

Thanks for the warm welcome, and for the helpful context!

Unfortunately, upgrading isn't an option for us at the moment due to constraints in our current environment. We're aware that 5.2.2 is well past EOL, and moving to a supported version is on our roadmap — but for now we need to work within the existing setup.

With that in mind, is there any guidance you could share for our current situation? Appreciate the help!

I am also troubled by this same issue. Could you please advise me on how to resolve the problem of reCAPTCHA verification failure

Thanks for confirming @2580782185 and @gbl0915. I'm following up internally to see if I can get an answer for you regarding getting a license. But my recommendation would definitely be to upgrade to a supported version sooner rather than later.

I'll let you know when I have a response.

Hope that helps!

Hello, has this issue been addressed? Today, I visited the website Register | Elastic and noticed that the issue of "reCAPTCHA fails to load" still persists.

Hi @2580782185,

Thanks for getting in touch again. The team are currently looking at the issue, so at the moment I don't have a further update for you. I'll revert back when I have an update.

But I would note as discussed with @gbl0915 we would strongly recommend upgrading to a version within support as per our EOL policy.

Hope that helps!

Carly

Do you have a fully functional, working system right now?

If not, there's 2 ways you can progress.

  1. Wait for Elastic to maybe fix the reCAPTCHA issue, over which you have no control and no SLA. They might fix it, might not, I've no idea which, but it's for a longggg EOL-ed software version.
  2. Upgrade, which is within your control. That this is in your "roadmap" is to me quite depressing. Sorry, I don't walk in your shoes, but Elasticsearch 5.2.2 was released in Feb 2017 ! Thats not a typo, 2017.

There’s an old proverb that often gets quoted in these situations: If it works, don’t touch it. Until it stops working, then act surprised.

We're also experiencing this issue. Upgrading is not a realistic option at the moment for us either.

@nhoviolsen we're following up internally and will send an update when we have one. But I would been keen to understand why upgrading is not a realistic option for you given 5.2 is long past EOL.

Let us know!

@gbl0915

I can see the captcha loading , maybe the issue is fixed. you can answer the query raised by @carly.richmond

Thanks!!

Correct @Tortoise the team have managed to fix the issue. @2580782185 and @gbl0915 you should now be able to use the portal to renew your licenses. But as we mentioned before we definitely recommend upgrading to an in-support version.

Hope that helps!

Thanks for Elastic Team :oncoming_fist: