And for the love of god, can we PLEASE document the fixes we’re finding along the way.

I’m currently impacted by the user registration bug that relates to user constraints in the DB - and it’s completely ruining what would be an amazing launch. However, apparently some other server owners have it working! Buuuuuttt, no one is posting their secrets - and it’s really hampering my ability to deliver this instance.

So, please, someone explain how I fix this issue and get a working instance.

Do I need to roll back? If so, what version? Do I need to run some PSQL? Do I need to patch some Rust?

EDIT: SUCCESS!

Here is the sacred knowledge for my particular situation.

It was half PEBKAC and half bug -

The PEBKAC - If using protonmail SMTP - you’ll need ‘starttls’ for it to work.

If SMTP is broken in this way, it seems to cause a bug in user creation that will essentially create partial data that would prevent user creation with the same name from occuring again. You can use a “plus” address (ie [email protected]) to work around this in the meantime.

  • tucsocial-adminOPA
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    Final-ish comment on this:

    Here are the valid workarounds to this issue:

    1. Turn off email validation and enable captchas (if doing open registration like I am)
    2. Turn on the registration from, and disable captchas.
    3. Fix your SMTP settings
    4. For anyone impacted by a failed registration, have them use a “plus” email address like ( [email protected] ) after you have it fixed.