# Broken password confirmation box on registration

**URL:** https://meta.discourse.org/t/broken-password-confirmation-box-on-registration/318386
**Category:** Bug
**Tags:** fixed
**Created:** [July 25, 2024, 3:18pm UTC](https://meta.discourse.org/t/broken-password-confirmation-box-on-registration/318386 "2024-07-25T15:18:51Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![luftaquila](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/luftaquila/32/434823_2.png) [@luftaquila](https://meta.discourse.org/u/luftaquila)
#### Post date: [July 25, 2024, 5:23pm UTC](https://meta.discourse.org/t/broken-password-confirmation-box-on-registration/318386/4 "2024-07-25T17:23:38Z")

</div>

My instance’s first member suffered from the “We cannot detect if your account was created, please ensure you have cookies enabled” message while signing up, which is accounted here: [We cannot detect if your account was created, please ensure you have cookies enabled](https://meta.discourse.org/t/we-cannot-detect-if-your-account-was-created-please-ensure-you-have-cookies-enabled/109626)

I spent a hour reading that topic, and finally realized that the hash boxes are some canary logic. Successfully reproduced the “We cannot…” issue by editing that hash for even a character. Maybe it will be fixed too, by hiding that challenge boxes. 2-in-a-row.

I found another instance that is affected([https://discourse.jupyter.org/](https://discourse.jupyter.org/)) and now I’m surprising about how instances could be remotely affected, even if I didn’t change things after I successfully signed up with no issue.

I’m not sure that `./launcher rebulid app` automatically pulls the latest commit that broke signup, but I think I did rebuild instance to install some plugins before the issue was present. Maybe this is the cause.

---

_[View the full topic](https://meta.discourse.org/t/broken-password-confirmation-box-on-registration/318386)._