Hi all, Just as the title says. discourse-doctor will connect to my mailserver (running on the host machine) via its external and internet-facing interface (but not localhost), but discourse itself just will not. No attempt by discourse is being logged, neither in the Rails production log nor my m…

So running the mail test at /admin/email doesn’t send a message? Is /sidekiq running? Did you do a standard install ? Discourse needs a domain name to work, so your problem may be related to binding it only to localhost.

Hi Jay, thanks for responding. When I run sudo docker exec -it app /bin/bash, I don’t see an /admin directory. Nor do I see an /admin directory cloned from the git repo. pgrep -afl sidekiq does show a process with that name running. I am running Discourse behind HAProxy, as I described here, henc…

I have tried modifying expose as follows and there is still not so much as a SYN being sent to port 587 on my mailserver. DISCOURSE_HOSTNAME is set to the correct domain, sidekiq is running, and still no idea where to find /admin/email. expose: - "1234:80" # http

Activation emails: discourse-doctor works, discourse itself does not

Support Self-hosting

itsbhanusharma (Bhanu Sharma) October 20, 2019, 11:10am 5

/admin/email is a relative path
You need to access it in a web browser:
{Your Discourse Hostname}/admin/email

Topic		Replies	Views
Announcing Discourse Doctor Development	13	7173	April 24, 2025
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4236	September 20, 2022
Cannot send mail with Discourse on new install but can from command line (on digital ocean) Self-hosting	8	2424	June 1, 2020
Verification Email will not send due to errors caused by Docker filesystem Self-hosting email	23	7142	September 4, 2015
How to get Discourse to work with Postfix Self-hosting	17	2771	November 4, 2021

Activation emails: discourse-doctor works, discourse itself does not

Related topics