Docker Errors with Discourse | nginx 502 bad gateway docker
HelloDockerCommunity,RecentlyI’vemovedmyDellServerfromonelocationtoanother.ItsMainOS/VMManagerisProxmoxVE5.3.IgotanNginxVMthatisReverseProxyingseveralotherVMs,oneofwhichisaDiscourseVM.ThisVMwasdisplayedDiscoursepreviouslyinmyoldnetwork…butnow,it’sreportingDockerErrors.Letmeexplain:AfterconfiguringmynewRouter,IgotmyotherVMsreverseproxyingthroughtheNginxVMtoconnecttotheInternetproperlywithnorealwork.TheonlyissuehasbeenDiscourse,whereIamreceiving502BadGateway-nginx/1.14.0(Ubuntu)whentryingtoacc...
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.[1] To summarize: I discovered earlier today that when I try to start, stop, restart or rebuild Discourse, I received the following errors:
...