# Discourse doctor DNS issue with reverse proxy

**URL:** https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698
**Category:** Self-hosting
**Created:** [December 18, 2020, 11:41am UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698 "2020-12-18T11:41:42Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Andro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andro/32/173721_2.png) [@Andro](https://meta.discourse.org/u/Andro)
#### Post date: [December 18, 2020, 11:41am UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698/1 "2020-12-18T11:41:42Z")

</div>

What does this error signify?

```plaintext
Discourse version at discourse.jackrail.space: Discourse 2.7.0.beta1
Discourse version at localhost: NOT FOUND
==================== DNS PROBLEM ====================
This server reports NOT FOUND, but discourse.jackrail.space reports Discourse 2.7.0.beta1 .
This suggests that you have a DNS problem or that an intermediate proxy is to blame.
If you are using Cloudflare, or a CDN, it may be improperly configured.

```

I am running Discourse reverse proxied via nginx.

---

<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: [December 18, 2020, 12:37pm UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698/2 "2020-12-18T12:37:31Z")

</div>

My understanding is that discourse doctor is limited to the vanilla install with internal nginx and somehow it can’t read the discourse version string when you’re using a reverse proxy with discourse. it isn’t something to be bothered about if you already know that you have a reverse proxy that is working fine. You can safely ignore this warning.

---

<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: [December 18, 2020, 3:26pm UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698/3 "2020-12-18T15:26:12Z")

</div>

What problem are you trying to solve?

---

<div class="post-metadata">

### Author: ![Andro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andro/32/173721_2.png) [@Andro](https://meta.discourse.org/u/Andro)
#### Post date: [December 19, 2020, 1:02am UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698/4 "2020-12-19T01:02:37Z")

</div>

Non delivery of emails by Amazon SES. I am looking at _everything_, so I tried running the doctor.

Yes, my reverse proxy is running fine.

---

<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: [December 19, 2020, 1:07am UTC](https://meta.discourse.org/t/discourse-doctor-dns-issue-with-reverse-proxy/173698/5 "2020-12-19T01:07:02Z")

</div>

Then your can ignore that error.
