# Is this a discourse or dns issue

**URL:** https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021
**Category:** Self-hosting
**Created:** [6월 16, 2018, 2:26오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021 "2018-06-16T14:26:37Z")
**Posts on this page:** 11
**Page:** 2

<div class="post-metadata">

### Author: ![SamBehner2](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@SamBehner2](https://meta.discourse.org/u/SamBehner2)
#### Post date: [6월 16, 2018, 3:25오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/21 "2018-06-16T15:25:51Z")

</div>

When I did the netstat for “:80 “ it returned nothing, same with 443

(had to make new account to continue conversation because I had some new member limit)

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [6월 16, 2018, 3:27오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/22 "2018-06-16T15:27:27Z")

</div>

hahaha, new account, sneaky 🕵️‍♂️

I’d do a rebuild of the app:

```plaintext
cd /var/discourse
git pull
./launcher rebuild app

```

---

<div class="post-metadata">

### Author: ![SamBehner2](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@SamBehner2](https://meta.discourse.org/u/SamBehner2)
#### Post date: [6월 16, 2018, 3:30오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/23 "2018-06-16T15:30:42Z")

</div>

It says “Device docker0 does not exist cannot connect to docker daemon”

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [6월 16, 2018, 3:32오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/24 "2018-06-16T15:32:00Z")

</div>

> [@SamBehner2](#):
>
> Device docker0 does not exist cannot connect to docker daemon

what is the underlying OS? is it 64-bit? Suggest Ubuntu LTS variant.

---

<div class="post-metadata">

### Author: ![SamBehner2](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@SamBehner2](https://meta.discourse.org/u/SamBehner2)
#### Post date: [6월 16, 2018, 3:32오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/25 "2018-06-16T15:32:48Z")

</div>

It’s Ubuntu 18.04 and yes it’s 64 bit

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [6월 16, 2018, 3:34오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/26 "2018-06-16T15:34:06Z")

</div>

Here’s a good Topic on Docker install:

> [@Device "docker0" does not exist](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/35):
>
> Restarting the docker using the following command solved the issue: ./launcher stop app ./launcher start app Thanks everyone!

Try that?

---

<div class="post-metadata">

### Author: ![SamBehner2](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@SamBehner2](https://meta.discourse.org/u/SamBehner2)
#### Post date: [6월 16, 2018, 3:35오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/27 "2018-06-16T15:35:07Z")

</div>

Ok will check it out!

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [6월 16, 2018, 3:44오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/28 "2018-06-16T15:44:11Z")

</div>

I’d be skeptical it’s a broken install in case nothing is listening on 80 & 443.

I’d suggest start afresh instead of diagnosing because your forum isn’t launched yet, Just reformat that server and follow the install guide properly.

Your DNS records are fine I’ve just confirmed that.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [6월 16, 2018, 3:47오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/29 "2018-06-16T15:47:51Z")

</div>

But Bhanu if you view source there is HTML and its a basic Ember skeleton … why would that be if its a firewall? Surely that would block it completely?

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [6월 16, 2018, 3:53오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/30 "2018-06-16T15:53:08Z")

</div>

That’s being injected by your ISP or something because I’ve tried to access in browser (Unable to connect) and curl from my servers and response was (connection refused) so it’s definitely something specific to you I guess.

Ps: if you see from inside his vps, nothing is listening on Ports 80 or 443 so it’s definitely your DNS trying to load some content. what DNS do you use?

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [6월 16, 2018, 3:55오후 UTC](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021/31 "2018-06-16T15:55:09Z")

</div>

Interesting idea … by why include an Ember header? It’s a blank page too, not even a helpful message 🙂

[이전 페이지](https://meta.discourse.org/t/is-this-a-discourse-or-dns-issue/90021.md?page=1)
