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 er…

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

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

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 draait succesvol, kan geen toegang krijgen tot discourse hostnaam

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 1 oktober 2025 om 09:54 4

Uw DNS-record wijst niet naar uw server. Dat is wat de verbindingscontrole controleert.

Topic		Antwoorden	Weergaven
Browser can't connect to server Self-hosting	5	1467	26 januari 2020
Troubleshooting Port Access Self-hosting	25	1631	18 augustus 2020
Unable to connect to discourse after installtion Self-hosting	3	321	14 februari 2024
Discourse help on digitalocean Self-hosting	9	762	7 juli 2020
Can't access site after installation Self-hosting	10	4130	14 april 2016

Discourse docker draait succesvol, kan geen toegang krijgen tot discourse hostnaam

Gerelateerde topics