fix/website-network
main
The rename changed the network resource's name and not the container's network, so the container looked for a network that no longer exists and the site answered 502 (2026-09-30).