This message was deleted.

Hey 👋 Do you have some logs from the server container? Also, do you maybe have some firewall (ufw, firewalld, etc) active?

Nope, no firewall. I don't think this is specifically a

k3d

issue the more I think about it. Docker containers configured to use user defined networks or the default bridge network have broken networking. Published ports don't work, unable to reach other containers, unable to reach the Internet, etc.