The user laplasz is troubleshooting an issue where the discourse-doctor fails to initiate a connection to the SMTP server, despite the website sending emails successfully. They want to debug the rake emails:test command to confirm if packets are being sent to the configured SMTP address and port, but no traffic is visible via tcpdump. pfaffman suggests referring to existing guides on email troubleshooting and running the rake task directly, modifying the YAML, and restarting the container. laplasz clarifies that the issue is with the debugging tool itself and asks if a Ruby debugger like ruby-debug is available in the app image. Nikolai_Patrushev comments on the lack of comprehensive YAML validation, suggesting a missing configuration value may be the cause.
Hi There!
So the website can send out emails using the configured smtp server. However the discourse-doctor does not.
So how can I debug the rake 'emails:test[user@domain.my]' command.
I would like to see that there are packets going towards the address which was configured with SMTP_ADDRESS and SMTP_PORT
right now using tcpdump there is no any packet going out towards that address.
Thanks
If you want to debug your smtp then see Troubleshoot email on a new Discourse install - #547 by Nikolai_Patrushev or perhaps Troubleshooting Outgoing Email. Discourse-setup isn’t really the best way.
Just run the rake task yourself, then edit the yml and destroy and start the container then exit and try again.
so again - the troubleshooting tool itself seems to not working - that is why I am asking how to debug emails:test task - for example see debug printouts during execution - there is a tool rdebug and the command would be ruby-debug rake my:task
is there something similar available in the app image?
Thanks
As always verbosity kills motivatio.
No for real as far as i remember , there was missing value in yml file.
I still amazed how some developers dont track all possible valid yml options