Ah, our nginx-proxy image is old. We probably don't have that change, then.
And besides, adding expose: 8080 made element.data.coop work again...
Maybe. That issue was not exactly about this, but it's there I learned about nginx-proxy and its expectations about EXPOSE.
The EXPOSE is necessary because it tells docker (and thus nginx-proxy) what ports the container is listening on. Nginx-proxy will otherwise treat the container as being down resulting in annoying…
It can also be confirmed on our host:
reynir@hevonen:~$ sudo netstat -tlnp expose doesn't expose the port publicly. It's like writing `EXPOSE…
Well, UDP is connectionless and doesn't know about requests and responses. The reply is sent to the sender on the sending port. It may be that the rule generated by ufw tracks the state and allows…
What does "omits the firewall" mean?
It means that if UFW denies port 80, but a Docker container exposes
80:80, it won't be blocked. This is due to Docker interacting with iptables/nft…
What does "omits the firewall" mean?
If we can undo the change and won't lock ourselves out I think we should try it.
Yes, I think it's only used internally. Whether we have configured things correctly to use internal networks is another question. I don't know all that much about LDAP, and especially regarding…