Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to complete sign-up with Chrome - error displaying captcha. #15410

Closed
tim-seoss opened this issue Oct 7, 2020 · 11 comments
Closed

Unable to complete sign-up with Chrome - error displaying captcha. #15410

tim-seoss opened this issue Oct 7, 2020 · 11 comments
Labels
A-Registration P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation

Comments

@tim-seoss
Copy link

Unable to complete sign-up with Chrome - error displaying captcha.

Whilst trying to complete a user sign-up in element web, on macOS Chrome, the following is displayed:

This homeserver would like to make sure you are not a robot

[Empty boxes]
Error: reCAPTCHA has already been rendered in this element

Steps to reproduce

  • Attempt to sign up to more than one Matrix account (on the Matrix.org home server) in succession with Chrome on macOS
  • At captcha challenge, the error described is displayed

Logs being sent: yes/no

Version information

  • Platform: web (in-browser)

For the web app:

  • Browser: Chrome - macOS Chrome Version 85.0.4183.121 (Official Build) (64-bit)
  • OS: macOS
  • URL: app.element.io
@t3chguy
Copy link
Member

t3chguy commented Oct 7, 2020

Do you have any chrome extensions? Does the error occur if you run in incognito?

@tim-seoss
Copy link
Author

tim-seoss commented Oct 7, 2020

No chrome extensions. After going back to the site later, the error did not occur (but this I think was because the captcha flow wasn't triggered - it presumably is a rate-limit thing?) I am reporting this error on behalf of another user, sorry, omitted the screenshot from the original message. Please see attached:
Screenshot 2020-10-06 at 12 45 53

@tim-seoss
Copy link
Author

Hmm, looks like there are extensions installed from that screenshot, I'll check with the user what they are.

@tim-seoss
Copy link
Author

See attached screen-shot for the user's Chrome Extensions
Screenshot 2020-10-07 at 16 54 12

@t3chguy
Copy link
Member

t3chguy commented Oct 7, 2020

Best if they can try with them disabled, like in incognito.#

Does the error occur if you run in incognito?

@tim-seoss
Copy link
Author

Sorry, I won't be able to get this user to retry because they're already unimpressed with Matrix / Element due to numerous UI/UX sharp edges and bugs. Also I believe that this captcha isn't on the normal sign-up path, but is only triggered as part of a rate-limiting / anti-abuse path (is that correct?), and so would be hard to reproduce anyway?

I appreciate your point about extensions, but the above list looks reasonably innocuous / non-invasive.

@t3chguy
Copy link
Member

t3chguy commented Oct 7, 2020

Nope, captcha is always on the registration path if the homeserver has it configured. matrix.org is one such server.
I guess nothing stops a server doing it based on rate-limiting but existing software doesn't

@tim-seoss
Copy link
Author

Thanks. This was pointing at matrix.org. I can try and reproduce this myself, but I don't have a Mac, so this seems like it might not be a good idea.

The user later succeeded at the sign-up (without using Incognito mode I believe), so it looks like this is something intermittent.

Without knowing the underlying implementation, perhaps this is some sort of race internal on code running on the browser, or possibly something triggered by network errors, server latency etc.

@tim-seoss
Copy link
Author

Perhaps it would be possible to trigger this error in a reproducible way via a code modification, and then implement a retry, or at the very least a more friendly, helpful error message suggesting that the user retry and/or try to use an incognito window?

@turt2live turt2live added P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Registration labels Oct 9, 2020
@jryans jryans added the defect label Feb 8, 2021
@jryans
Copy link
Collaborator

jryans commented Feb 8, 2021

At the moment, I am not quite sure what to do with this report, as so far we only have one report of this, and it would be ideal if we could find a way to reproduce or understand the cause.

Perhaps the related issue #16379 will be enlightening once resolved.

@t3chguy
Copy link
Member

t3chguy commented Jun 8, 2023

Closing due to no repro in 2 years

@t3chguy t3chguy closed this as completed Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Registration P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation
Projects
None yet
Development

No branches or pull requests

4 participants