Closed n10u53 closed 3 years ago
The problem that withheld me from accessing the instance was a nginx error, 502 duuhh... Folowing these steps here fixed it, not exactly sure why, new to docker and pretty late now. So I'll be checking that out tomorrow!
But that still doesn't explain why sso and admin are unhealthy, and why they are throwing these errors...
I had the exact same issue yesterday. My issue had to do with Docker networking not playing nice with firewalld with nftables backend. Are you on Centos / RHEL / Fedora by any chance?
The msql container was not reachable, causing SSO and Admin containers to fail. The web container as well was not reachable, causing nginx to throw 502s. Both containers did not have web access either. ICMP does work, but no tcp.
What worked for me was to change the firewalld backend to iptables (in /etc/firewalld/firewalld.conf, then restart firewalld, then restart docker).
Google "firewalld nftables docker" for more info ;)
I had the exact same issue yesterday. My issue had to do with Docker networking not playing nice with firewalld with nftables backend. Are you on Centos / RHEL / Fedora by any chance?
The msql container was not reachable, causing SSO and Admin containers to fail. The web container as well was not reachable, causing nginx to throw 502s. Both containers did not have web access either. ICMP does work, but no tcp.
What worked for me was to change the firewalld backend to iptables (in /etc/firewalld/firewalld.conf, then restart firewalld, then restart docker).
Google "firewalld nftables docker" for more info ;)
This might very well be my problem yes, I am using Centos. I will check this out and update the awnser with the outcome! Thanks alot! :D
I had the exact same issue yesterday. My issue had to do with Docker networking not playing nice with firewalld with nftables backend. Are you on Centos / RHEL / Fedora by any chance?
The msql container was not reachable, causing SSO and Admin containers to fail. The web container as well was not reachable, causing nginx to throw 502s. Both containers did not have web access either. ICMP does work, but no tcp.
What worked for me was to change the firewalld backend to iptables (in /etc/firewalld/firewalld.conf, then restart firewalld, then restart docker).
Google "firewalld nftables docker" for more info ;)
This did indeed fix my issue. I googled around for some other solutions regarding this issue but none of them worked. Your's did right out of the box though! Thanks! Any insights on why the one does and the other doesn't work or what make the difference between the two?
I'm afraid I'm not knowledgeable on how iptables-nftables work together and how Docker handles its firewalling to explain in detail. But after struggling with a few similar issues like this in the past few days, I'm learning :)
How I understand it, if firewalld has the nftables as backend, the iptables command still works to push changes, but they don't reflect the single source of truth anymore. Docker doesn't know about nftables, and pushes its rules through iptables (which should work), but it also uses the iptables command to see which rules are in place. And seeing there are rules in place iptables -L or -S doesn't know about some things will go wrong. Using iptables as backend seems like the easy solution for now (other than handling your lowlevel firewall rules manually).
Disclaimer: not an expert here, so if anyone feels the need to correct, please do ;)
Hello I am trying to get on-premise hosting working and bitwarden throws an Bad Gateway error. Even when curling on the machine hosting the bitwarden instance. So this has nothing to do with my own world-facing proxy.
"docker ps" shows all things working, even bitwarden-mssql, except for -admin and bitwarden-sso. They both refer to some database error. The bitwarden-mssql shows some errors, but no obvious hard-errors? I am not knowledgable with mssql so could be wrong there... Any advice would be welcomed!
I have tried executing "./bitwarden.sh updatedb" in the hope this would fix anything/show some usefull fails but it says the update and migration was succesfull?? I must be completely overlooking something but I have don't even have the slightest clue what that could be...
bitwarden-sso log:
bitwarden-mssql log:
bitwarden-mssql log: