So, emails are failing en masse once again on my site. [afbeelding] This situation happened once before (in January), and restarting Discourse “fixed” it. But due to the very nature of the problem, there’s no good way to stay informed about whether there is a problem or not. In this episode, emai…

Just stopped and started Discourse and it is still unable to send email. Here is a backtrace from GET /logs: /usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `initialize' /usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `open' /usr/local/lib/ruby/2.0.0/net/smtp.rb:541:in `tcp_socket' /usr/local/lib/ruby/2…

Do your box can resolve the DNS of the your stmp address? In other words can you dig it? dig smtpaddress.com

It’s the third DNS problem report in this week… :pokerface: This might be helpful: [afbeelding] Initial email failure. Job exception: getaddrinfo: Name or service not known Self-hosting Probably Discourse can’t figure out DNS for your <mycompany>.com. Set …

Hi @Falco + @fantasticfears . Thanks a lot for your responses. I got email working again after a little effort today. Adding the --dns options in /etc/default/docker and restarting docker with sudo service docker restart did work. I was able to open a /bin/bash inside the Discourse container and exe…

Jobs::HandledExceptionWrapper: Wrapped SocketError: getaddrinfo: Name or service not known

Support

fantasticfears (Erick Guan) 16 april 2016 om 18:24 4

It’s the third DNS problem report in this week…

This might be helpful:

Topic		Antwoorden	Weergaven
Initial email failure. Job exception: getaddrinfo: Name or service not known Self-hosting	4	4531	13 juni 2017
I give up with email Support email	3	172	16 april 2025
Email don't send Support email	1	426	24 augustus 2023
Latest version of Discourse not sending Email Self-hosting email	7	564	2 juli 2024
Can’t send emails due to failed internal dns resolution Support	16	3037	17 januari 2019

Jobs::HandledExceptionWrapper: Wrapped SocketError: getaddrinfo: Name or service not known

Gerelateerde topics