Docker Errors with Discourse: 502 Bad Gateway - nginx/1.14.0 (Ubuntu) + Unable to find image locally + Error response from daemon

Hello Docker Community,

Recently I’ve moved my Dell Server from one location to another. Its Main OS/VM Manager is Proxmox VE 5.3. I got an Nginx VM that is Reverse Proxying several other VMs, one of which is a Discourse VM. This VM was displayed Discourse previously in my old network … but now, it’s reporting Docker Errors. Let me explain:

After configuring my new Router, I got my other VMs reverse proxying through the Nginx VM to connect to the Internet properly with no real work. The only issue has been Discourse, where I am receiving 502 Bad Gateway - nginx/1.14.0 (Ubuntu) when trying to access Discourse in a Browser.

I have received this error before, but usually it’s a simple Discourse Restart or Reboot. See this linked Discourse Topic for more details on what I’ve attempted, and the results of them. To summarize: I discovered earlier today that when I try to start, stop, restart or rebuild Discourse, I received the following errors:

Unable to find image ‘discourse/base:2.0.20191013-2320’ locally
/usr/bin/docker: Error response from daemon: Get Get net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See ‘/usr/bin/docker run --help’.
Your Docker installation is not working correctly

Right now these errors don’t come up after attempting several Discourse Rebuilds, but then it the site is still reporting 502 Bad Gateway - nginx/1.14.0 (Ubuntu) and I can still trigger the Unable to find image and Error response from daemon messages in other ways:

root@forum:~# docker run ubuntu
Unable to find image ‘ubuntu:latest’ locally
docker: Error response from daemon: Get net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See ‘docker run --help’.

So I suspect I have some of the Docker packages, but not all the necessary ones. And something where “my Server can’t connect to the Docker Hub in order to download large images.” (I don’t think I’m using Docker Hub however)

Does anyone have any recommendations on what I should be trying to do to resolve this issue? Keep in mind that I really don’t know Docker. I only have it installed because it’s required for Discourse to work. I should also note that the only thing I’ve had to do with docker in Discourse in my old network was just to install it. Since I moved, I’m now using a new router and a new ISP, this is the first time I’ve experienced this problem, so I am wondering if maybe it could be a setting on the Router or the ISP itself, and not some setting in the Discourse VM?

Anyways, I’ve come to this forum on recommendation from a Discourse Forum user.

If this is in the wrong Category, please feel free to move this Topic.

I resolved my Docker issue. See this post in the Discourse Forums for more details.

Also turns out there was an Nginx Reverse Proxy issue as well. This was resolved in this post. Discourse shows up just fine now.