It suggests to me that docker networking is broken, so even if Discourse and redis are working properly, Discourse cannot access redis because networking and/or docker are broken.
My guess is that these problems appeared sometime after you installed firewalld. and that’s what broke your installation.
I have done some progress. my config is using apache 2.4 as proxy. In my config, I have added the following:
RemoteIPHeader X-Forwarded-For
To keep track of the original IP address.
After httpd restart, I was able to access the discourse (with an alert about the ssl certificate expiration). I have fixed that one too and now everything is working well but with firewalld disabled.
I have found many posts about issues between docker and firewalld on centos 7. I will so switch back to iptables.
About the redis error message, after the above steps, this one only appears when docker is stopping. At restart, it’s not displayed so I would think this is ok.
Thx!
2 Likes
csmu
(Keith John Hutchison - Ceiteach Seán Mac Úistin)
7
After reading this I stopped Docker on our Centos server