According to this post, I thought the new recaptcha API was used network-wide. Though today, when going to SEDE (which for whatever reasons never recognized me automatically), I got this message instead of a usable captcha image.

V1 Unsupported
Please direct siteowner to g.co/recaptcha/upgrade

(Doing a second try doesn't show this message anymore, and the recaptcha v1 works as intended.)

According to the linked page, the reCAPTCHA v1 API will stop working on March 31, 2018:

What happens to reCAPTCHA v1?

Any calls to the v1 API will not work after March 31, 2018. Starting in November 2017, a percentage of reCAPTCHA v1 traffic will begin to show a notice informing users that the old API will soon be retired.

Most websites around the world have already switched to reCAPTCHA v2, where humans pass effortlessly. With our advanced risk analysis engine, reCAPTCHA v2 can effectively separate humans from bots and always stay ahead of the attackers.

If your site still uses reCAPTCHA v1, please upgrade to reCAPTCHA v2 immediately. We no longer support reCAPTCHA v1. Any calls to the v1 API will not work after March 31, 2018. Please register a new key and upgrade to v2.

I'm really hoping this will not take 6 to 8 weeks to fix, because we've only got three and a half weeks left!

  • 4
    SEDE is not an actual part of the network, and often gets forgotten for things like this since it's an open source project not completely maintained by us. (That's also why your session for the rest of the network doesn't work on SEDE - completely separate and disjoined auth system there.)
    – animuson StaffMod
    Jan 21, 2018 at 6:43
  • @animuson ah I didn't know about that. Then should I contact someone else or is this the correct place anyway?
    – Kaiido
    Jan 21, 2018 at 7:05
  • 1
    Here is a good place. The new code still has to be deployed to our instance whenever it gets updated.
    – animuson StaffMod
    Jan 21, 2018 at 7:08
  • 21
    FWIW, I just got the same message, and it turns out that entering "V1 UNSUPPORTED" in the text box does pass the test. :D Jan 21, 2018 at 12:34
  • 2
    For me nearly the same, but now I also get an accurate date when the shutdown will happen. It's March 31 this year. gstatic.com/recaptcha/images/v1_unsupported.png
    – Filnor
    Feb 20, 2018 at 12:46
  • 2
    I'm afraid we're out of luck... Tim Stone appears to be no longer involved with SEDE, and there's nobody else to change the required code. Likely SEDE will just shut down at some point. Feb 26, 2018 at 9:45
  • It would be nice if they could use the same captcha as on all other sites where you just need to check a checkbox and don't have to type anything. Feb 26, 2018 at 14:09
  • 10
    Doom da doom doom doooom. I'll fix the code this week, so presuming someone can deploy things will magically work out
    – Tim Stone
    Mar 6, 2018 at 21:18
  • @TimStone Thank you, but could you maybe consider open-sourcing the SEDE code if you're permitted to, to prevent this sort of thing from becoming an issue again?
    – Ian Kemp
    Mar 7, 2018 at 11:42
  • 4
    @IanKemp Data Explorer has always been open source
    – Tim Stone
    Mar 7, 2018 at 17:16
  • @DonaldDuck That's exactly what they now have to do.
    – Tim
    Mar 10, 2018 at 22:20
  • @TimStone week later, curious to know if you fixed anything? Mar 13, 2018 at 9:15
  • 1
    @ShadowWizard Yep, I did the replacement, I'll put out the pull request later and add an answer
    – Tim Stone
    Mar 13, 2018 at 9:31

1 Answer 1


A fix is merged now and seems to be live (thanks Nick!)

  • 1
    I might look into the invisible recaptcha later to avoid the whole submit -> captcha -> resubmit thing later, but there's a whole list of things that need cleaning up in that codebase
    – Tim Stone
    Mar 27, 2018 at 20:14
  • I came here just to say that the new capcha is AWESOME and so much easier than the old one. Mar 29, 2018 at 15:50
  • Nope. What went wrong? Any idea? :/ Apr 2, 2018 at 19:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .