Horus
June 5, 2017, 6:25pm
1
Hello,
I just did a fresh setup of my discourse installation. The existing one was for testing and so on, now I’m going to production.
Since I’m hit by https://meta.discourse.org/t/first-mail-validation-mail-never-sent/62952 I resend the activation mail for users.
I have a user that is approved, but not yet active, since he didn’t replied to the activation mail so far. I try to resend it, but only get
(original) Du hast nicht die Erlaubnis, die angeforderte Ressource zu betrachten.
The user is trust level 1 (I start from 1)
I work with the default administrator. It says:
Administrator: yes
I recently deactivated the bootstrap mode, the forum banner says it’s due to be deactivated in the next 24 hours.
I am bit surprised that I’m not moderator, though it’s probably included in Administrator.
Why can’t I trigger resending the activation mail.
Thanks!
Horus
June 6, 2017, 7:57am
2
Ok, I’ve noticed another odd thing:
It seems that mail validation is completely disabled. When I sign up for a new test user it just says
Thanks for registration, we will notify you as soon as your account is approved.
Nothing about mail validation. Sending mails otherwise works fine. What could be the problem here?
enable local logins is checked, default trust level = 1
Sending a test mail works.
Already tried rebuilding the app
/logs/ shows this error:
[details=Backtrace]> /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/formatter.rb:46:in `generate’
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:721:in generate' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:752:ingenerate’url_for' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:280:incall’block (2 levels) in define_url_helper' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/polymorphic_routes.rb:239:inhandle_string_call’url_for' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/redirecting.rb:95:in_compute_redirect_to_location’redirect_to' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/flash.rb:57:inredirect_to’block in redirect_to' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:inblock in instrument’instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:ininstrument’redirect_to' /var/www/discourse/app/controllers/application_controller.rb:567:inredirect_to_login_if_required’block in make_lambda' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:164:inblock in halting’block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:504:ineach’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:inrun_callbacks ’_run_process_action_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:inrun_callbacks’process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rescue.rb:29:inprocess_action’block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:inblock in instrument’instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:ininstrument’process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/params_wrapper.rb:250:inprocess_action’process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:137:inprocess’process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiling_methods.rb:76:inblock in profile_method’dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rack_delegation.rb:13:indispatch’block in action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:74:indispatch’serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:inblock in serve’each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:inserve’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:25:incall’call' /var/www/discourse/lib/middleware/anonymous_cache.rb:138:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/flash.rb:260:incall’context' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/query_cache.rb:36:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:29:inblock in call’__run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in_run_call_callbacks’run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:27:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:incall’call_app' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:22:incall’call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:29:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/engine.rb:518:incall’call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:inpublic_send’method_missing' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:inblock in call’each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:incall’process_client' /var/www/discourse/lib/scheduler/defer.rb:85:inprocess_client’worker_loop' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:inspawn_missing_workers’start' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/bin/unicorn:126:in<top (required)>’load' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:22:in'[/details]
Another update:
I register, Discourse does not send a mail, nor does it states it will do so.
I immediately change the mail address in the “Thanks for registration” dialogue.
The mail is now sent to the new address.
Still, when I skip 2., there is no mail sent, nor can I request sending as an adminstrator.
Please help, as it basically breaks username/password based signup.
Thanks!
Sounds like email is not working? See the email troubleshooting #howto topic.
Horus
June 13, 2017, 8:59am
4
Mail is working just fine, please read my posts.
Sending mails otherwise works fine.
Sending a test mail works.
The mail is now sent to the new address.
Best Regards,
If you have manual account approval enabled, you must go to the pending user approval queue and approve the users.
Otherwise, disable “must approve users” in your site settings.
Horus
June 13, 2017, 12:53pm
6
Has this behavior changed recently? Because I remember: Signup -> Verification Mail -> Approval -> Approval Mail.
Now it seems Signup -> Approval -> Approval/Verfication Mail.
Best,
So you can confirm it is working for you? It is a bit of a
Horus
June 14, 2017, 9:53am
8
Me either, I’m fine with either. But I remember, that not too long ago, it was like I described above and I feel that behavior has changed.
Issue is solved therefore.
2 Likes
Great! Sorry about the confusion.
and 
problem between which comes first, the approval or the verification mail… I don’t have strong feelings about it either way.