Discourse doctor DNS issue with reverse proxy

What does this error signify?

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.

1 Like

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.

3 Likes

What problem are you trying to solve?

1 Like

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.

1 Like

Then your can ignore that error.

2 Likes