# Discourse docker runs successfully, cannot access discourse host name

**URL:** https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451
**Category:** Self-hosting
**Created:** [October 1, 2025, 9:20am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451 "2025-10-01T09:20:06Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Shin\_210](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shin_210/32/522110_2.png) [@Shin\_210](https://meta.discourse.org/u/Shin_210)
#### Post date: [October 1, 2025, 9:20am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/1 "2025-10-01T09:20:06Z")

</div>

After following [this docs](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md#1-preparing-your-domain-name), 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](https://meta.discourse.org/t/port-80-443-not-accessible-while-installing-discourse/280363/4). If I run “./discourse-setup” only, I’d get an error:

 ![Screenshot from 2025-10-01 16-37-21](https://global.discourse-cdn.com/meta/original/4X/a/3/0/a30d41f4ad43f1407631c29a4bdfea046400a5be.png)

 ![Screenshot from 2025-10-01 16-19-45](https://global.discourse-cdn.com/meta/original/4X/e/3/b/e3b72d323ae5a1e5633b1b8ff9e0842da410d0d8.png)  
 ![Screenshot from 2025-10-01 16-21-33](https://global.discourse-cdn.com/meta/original/4X/4/6/9/469fcec67c40a889f224d23fd3f93f4575e706b5.png)

---

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [October 1, 2025, 9:21am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/2 "2025-10-01T09:21:44Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Shin\_210](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shin_210/32/522110_2.png) [@Shin\_210](https://meta.discourse.org/u/Shin_210)
#### Post date: [October 1, 2025, 9:22am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/3 "2025-10-01T09:22:47Z")

</div>

yeah, I did, thank you.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 1, 2025, 9:54am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/4 "2025-10-01T09:54:32Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Shin\_210](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shin_210/32/522110_2.png) [@Shin\_210](https://meta.discourse.org/u/Shin_210)
#### Post date: [October 2, 2025, 2:59am UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/5 "2025-10-02T02:59:12Z")

</div>

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”

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [October 2, 2025, 5:43pm UTC](https://meta.discourse.org/t/discourse-docker-runs-successfully-cannot-access-discourse-host-name/384451/6 "2025-10-02T17:43:31Z")

</div>

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