Mailgun - no email, no mailgun log. no errors


#1

correctly setup mailgun. all greens for the dns. i have ran a curl command from the server to verify i could reach mailgun

curl command for testing

curl -s --user 'api:YOUR_API_KEY' \
    https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/messages \
    -F from='Excited User <mailgun@YOUR_DOMAIN_NAME>' \
    -F to=YOU@YOUR_DOMAIN_NAME \
    -F to=bar@example.com \
    -F subject='Hello' \
    -F text='Testing some Mailgun awesomeness!'

my production log after the resend verification email:

Started PUT "/finish-installation/resend-email" for 192.88.134.9 at 2018-05-17 22:11:09 +0000
Processing by FinishInstallationController#resend_email as HTML
  Parameters: {"authenticity_token"=>"xAq+IkcY+3FydAoOND/Yrn752F5ljSdbxZf85ETCA/aAgUBEeHR8a9BuqNJW4qE5Um5QwtT8/iabMjIWW6UWfA=="}
  Rendering finish_installation/resend_email.html.erb within layouts/finish_installation
  Rendered finish_installation/resend_email.html.erb within layouts/finish_installation (1.1ms)
  Rendered common/_special_font_face.html.erb (0.3ms)
  Rendered layouts/_head.html.erb (0.4ms)
Completed 200 OK in 40ms (Views: 3.3ms | ActiveRecord: 13.3ms)

there is no activity in the mailgun log for anything from discourse. i see the success log for the curl command. any ideas?


(Cameron:D) #2

Discourse doesn’t use the http API to send email so perhaps your host is blocking the SMTP port. In your Discourse mail configuration, what port is set?


(Jay Pfaffman) #3

Set the port to 2525 and it should work immediately.

Or you can file a ticket with your provider and hope that they’ll unblock the port sometime in the future.


#4

i’m not sure what happened, but after creating my admin account via console and logging into the system. I retried the failed emails and everything started to work after that.

thanks for the response though!