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.
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?
The second time I installed Discourse, I was having issues where emails wouldn’t send (same setup as you - internal SMTP at my company). It turned out that I had to configure Docker to find our DNS server because it couldn’t resolve the SMTP server.
I added this to the bottom of my DOCKER_OPTS: DOCKER_OPTS="--dns 172.X.X.X --dns 172.X.X.X"
@gvalchca I had a similar problem with an internal install of Discourse. I noted the fix in this thread. Basically, I had to add the address to the internal DNS server in the host machine’s Docker config file.
Discourse-doctor calls the rake task (inside the container). There were some changes to the rake task in the past day or so.
I submitted something last summer (?) that added to discourse-setup recommending to run discourse-doctor, they I think was never merged.
It might make sense to have discourse-setup run the rake task after the container gets cranked up. (I now run it routinely after I do an install, though I have to wait for the client to do the dns config before I do.)