After following this docs, I managed to get discourse up, but accessing the configured discourse host name returns 404. Is there anything wrong? Edit: for more information, I ran “./discourse-setup --skip-connection-test” as mentioned in this topic. If I run “./discourse-setup” only, I’d get an error: [Screenshot from 2025-10-01 16-37-21] [Screenshot from 2025-10-01 16-19-45] [Screenshot from 2025-10-01 16-21-33]

You might want to censor/blur out the SMTP info in your screenshot :wink:.

I did ping the domain and it pointed correctly to my server ip, just like the second link I attached on my post, that’s why I used “–skip-connection-test”

Then perhaps you have a firewall or something else blocking ports 80 and/or 443

Discourse docker runs successfully, cannot access discourse host name

Product Support Self-hosting

pfaffman (Jay Pfaffman) October 1, 2025, 9:54am 4

Your DNS record does not point to your server. That’s what the connection test checks.

Topic		Replies	Views
Browser can't connect to server Self-hosting	5	1559	January 26, 2020
Troubleshooting Port Access Self-hosting	25	2049	August 18, 2020
Unable to connect to discourse after installtion Self-hosting	3	391	February 14, 2024
Discourse help on digitalocean Self-hosting	9	924	July 7, 2020
Can't access site after installation Self-hosting	10	4274	April 14, 2016

Discourse docker runs successfully, cannot access discourse host name

Related topics