Dear Discourse community, Im having problems with my instance of Discourse. Although the servers parameters didnt change, and I am able to use them e.g. via simple Python script, the Discourse fails to send emails. It happened all of a sudden about a month ago after an update. I have rechecked the server parameters, apart from that I’m completely lost. Here is an error log: /usr/local/lib/ruby/2.0.0/net/smtp.rb:784:in `check_auth_args' /usr/local/lib/ruby/2.0.0/net/smtp.rb:548:in `do_start' /usr/local/lib/ruby/2.0.0/net/smtp.rb:520:in `start' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/smtp.rb:113:in `deliver!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.4/lib/mail/message.rb:2149:in `do_delivery' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.4/lib/mail/message.rb:237:in `block in deliver' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.6/lib/action_mailer/base.rb:543:in `block in deliver_mail' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.6/lib/action_mailer/base.rb:541:in `deliver_mail' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.4/lib/mail/message.rb:237:in `deliver' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.6/lib/action_mailer/message_delivery.rb:85:in `deliver_now' /var/www/discourse/lib/email/sender.rb:148:in `send' /var/www/discourse/app/jobs/regular/user_email.rb:41:in `execute' /var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Can you share your settings? (Makes sure you hide passwords though)

Hey, here they are: passwd is not needed, its a local server for internal use only: LANG: en_US.UTF-8 DISCOURSE_DEVELOPER_EMAILS: 'megan-community@informatik.uni-tuebingen.de' DISCOURSE_HOSTNAME: 'megan.informatik.uni-tuebingen.de' DISCOURSE_SMTP_ADDRESS: 'smtp.informatik.uni-tuebingen.de' # (mandatory) DISCOURSE_SMTP_PORT: 25 # (optional) DISCOURSE_SMTP_USER_NAME: 'megan-community@informatik.uni-tuebingen.de' # (optional) DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)

Now when i changed quotation marks, and wanted to rebuild app, it told me to update the Docker. Now Im unable to rebuild an app cause of that: fatal: unable to access 'https://github.com/SamSaffron/pups.git/': Could not resolve host: github.com Changing DNS and restarting docker like described here didnt solve it. Getting more and more frustrated…

Can you access github.com from your server (using ping or better curl)? Seems like a DNS issue or a network hiccup.

Looks like this: [image] How to restore your site from backup in the terminal? Self-hosting Follow the link. There is a detailed step showing how to do that. (1 - 5) For step 3, use DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" as this suggests:

Thanks a lot for your answers! Unfortunately nothing changed. Ping works, DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" is like its described. Docker was restarted, error when trying to rebuild remains the same,..

It looks like two different problems. Google’s DNS may just help you to access the wild on Internet. It’s for access the web. For email sending, I am not sure how it works.[quote=“gvalchca, post:3, topic:43592”] its a local server for internal use only: [/quote] You have set a DNS record for your SMTP server. How you prevent it from unauthorized access since you are exposing your username and claim it doesn’t need a password?

its only for the network inside of the institute.

Did you try this? cd /var/discourse git pull ./launcher rebuild app And the only error you are getting is DNS correct? If so then DNS is definitely not working from your server. The launcher script does not require the smtp setting to have a password.

Can’t send emails due to failed internal dns resolution

Product Support

codinghorror (Jeff Atwood) May 4, 2016, 2:58pm 8

Unable to resolve host is definitely a DNS problem, if that is the error you are seeing.

Topic		Replies	Views
Initial email failure. Job exception: getaddrinfo: Name or service not known Self-hosting	4	4649	June 13, 2017
Latest version of Discourse not sending Email Self-hosting email	7	667	July 2, 2024
Cannot receive the mail from email server Self-hosting	2	707	November 24, 2020
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	186111	April 27, 2026
Issues troubleshooting email Self-hosting	14	1268	April 25, 2019

Can’t send emails due to failed internal dns resolution

Related topics