So, emails are failing en masse once again on my site. [이미지] 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, emails have…

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: [이미지] 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 dns in …

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

Product Support

fantasticfears (Erick Guan) 4월 16, 2016, 6:24오후 4

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

This might be helpful:

글		댓글	조회수
Initial email failure. Job exception: getaddrinfo: Name or service not known Self-hosting	4	4607	6월 13, 2017
I give up with email Product Support email	3	235	4월 16, 2025
Email don't send Product Support email	1	466	8월 24, 2023
Latest version of Discourse not sending Email Self-hosting email	7	629	7월 2, 2024
Can’t send emails due to failed internal dns resolution Product Support	16	3174	1월 17, 2019

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

Related topics