Fout bij uitnodiging, interne serverfout

AI-generated summary

A user reports an internal server error when accepting an invite and during sign-up on talk.newpathconsulting.com, with an error stating the email is already in use. The issue is linked to a NoMethodError in the email_token.rb file, specifically due to an undefined token= method. Another user explains that the problem likely occurred because the database was migrated for an upgrade, but insufficient disk space prevented the new container from launching. If the issue is resolved, the user is advised to mark the solution.

I sent an invite to a friend and he is getting an internal error. Any place I can see logs for the background on this issue?

Also when trying to sign up at talk.newpathconsulting.com there’s an error during sign up. No matter what email I use I get “this email is already in use”. Anyone seen this before?

Here’s an info on an error that was close to the timing of the error

Message (3 copies reported)

NoMethodError (undefined method `token=' for #<EmailToken:0x00007fe0b9b72810>
Did you mean?  token_hash)
app/models/email_token.rb:9:in `block in <class:EmailToken>'
app/models/user.rb:1480:in `create_email_token'
app/models/invite_redeemer.rb:73:in `create_user_from_invite'
app/models/invite_redeemer.rb:123:in `get_invited_user'
app/models/invite_redeemer.rb:87:in `invited_user'
app/models/invite_redeemer.rb:167:in `approve_account_if_needed'
app/models/invite_redeemer.rb:91:in `process_invitation'
app/models/invite_redeemer.rb:8:in `block in redeem'
app/models/invite_redeemer.rb:6:in `redeem'
app/models/invite.rb:193:in `redeem'
app/controllers/invites_controller.rb:274:in `perform_accept_invitation'
app/controllers/application_controller.rb:399:in `block in with_resolved_locale'
app/controllers/application_controller.rb:399:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:356:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/request_tracker.rb:187:in `call'

Backtrace

activemodel (6.1.4.1) lib/active_model/attribute_methods.rb:469:in `method_missing'
app/models/email_token.rb:9:in `block in <class:EmailToken>'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:427:in `instance_exec'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:427:in `block in make_lambda'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:179:in `block (2 levels) in halting_and_conditional'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:603:in `catch'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:603:in `block in default_terminator'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:180:in `block in halting_and_conditional'
activesupport (6.1.4.1) lib/active_support/callbacks.rb:512:in `block in invoke_before'

Env

HTTP HOSTS: talk.newpathconsulting.com

I believe that issue was because the database had been migrated for an upgrade but disk space made it impossible to launch the new container.

@asirota if it’s working now, mark this as the solution.