Admin is not registering


(Karthikeyan A K) #1

Hi, I installed discourse on server, but I am unable to get past the “Register Admin Account”. I use elastic email, and its logs doesn’t seem to show that some system had contacted it to send the email.

I have updated and verified my DNS setting too. Is there any way on my server I can check the email messages, at least if there is a attempt to contact elastic email and it had failed. I checked in production.log and this is what I got

Started GET "/bea_wls_deployment_internal" for 116.117.157.69 at 2018-11-10 05:20:37 +0000
ActionController::RoutingError (No route matches [GET] "/bea_wls_deployment_internal")
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.0/lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
  Rendering exceptions/not_found.html.erb within layouts/no_ember
  Rendered exceptions/not_found.html.erb within layouts/no_ember (6.4ms)
  Rendered layouts/_head.html.erb (1.9ms)
  Rendered common/_special_font_face.html.erb (0.7ms)
  Rendered common/_discourse_stylesheet.html.erb (0.2ms)
  Rendered application/_header.html.erb (0.2ms)
  Rendering html template
  Rendered html template (0.0ms)
Started GET "/bea_wls_deployment_internal" for 116.117.157.69 at 2018-11-10 05:20:41 +0000
ActionController::RoutingError (No route matches [GET] "/bea_wls_deployment_internal")
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.0/lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
  Rendering exceptions/not_found.html.erb within layouts/no_ember
  Rendered exceptions/not_found.html.erb within layouts/no_ember (5.8ms)
  Rendered layouts/_head.html.erb (1.5ms)
  Rendered common/_special_font_face.html.erb (0.2ms)
  Rendered common/_discourse_stylesheet.html.erb (0.2ms)
  Rendered application/_header.html.erb (0.2ms)
  Rendering html template
  Rendered html template (0.0ms)
Started GET "/" for 116.117.157.69 at 2018-11-10 05:20:43 +0000
Processing by FinishInstallationController#index as */*
  Rendering finish_installation/index.html.erb within layouts/finish_installation
  Rendered finish_installation/index.html.erb within layouts/finish_installation (1.0ms)
  Rendered common/_special_font_face.html.erb (0.3ms)
  Rendered layouts/_head.html.erb (3.0ms)
Completed 200 OK in 11ms (Views: 6.3ms | ActiveRecord: 1.0ms)

Is there any way to solve it?


(Jeff Atwood) #2

That bea_wis thing is not part of discourse by default so it looks like you have added something?


(Karthikeyan A K) #3

Definitely not. I just downloaded the docker and followed the guides provided by discourse.


(Karthikeyan A K) #4

I am changing my site notification email now

rails r "SiteSetting.notification_email = 'discourse@yoursite.com'"

I think the default is noreply@sitename.com , mine is actually different. Reckon that might be causing the error.


(Jeff Atwood) #5

Maybe that odd path is coming from subdolder? You have opted into considerable pain if you are doing a subfolder install. It is far more complicated and there are lots of additional things that can go wrong.


(Karthikeyan A K) #6

I followed the exact installation given in official docs. Any way I will test my SMTP, that should give me a clue, then I can try it out on Discourse.


(Karthikeyan A K) #7

My Email settings are right . Looks like there is some deep problem, my discourse is in /var/discourse as mentioned in the document. Is there something wrong in the recently released docker image?


(Karthikeyan A K) #8

I created my admin account using rake task, now when I try to create a new signup I am getting this error

Completed 200 OK in 225ms (Views: 136.2ms | ActiveRecord: 34.3ms)
Sent mail to mindaslab@protonmail.com (30801.0ms)
Job exception: end of file reached

Sent mail to mindaslab@protonmail.com (30415.8ms)
Job exception: end of file reached

Sent mail to mindaslab@protonmail.com (30665.1ms)
Job exception: end of file reached

Have I run out of memory or something?


(Stephen) #9

Or, rather than blaming Discourse maybe troubleshoot your SMTP setup? 30,000ms indicates a timeout - which is likely a server communication issue.

A lot of server providers block outbound SMTP, requiring you to either contact them for ports to be opened, or swap ports.