[Self-Hosted] Fail to discover server using connect on login screen

Thanks! That explains the JavaScript error. However, my main concern wasn't actually the error itself, but the UX on self-hosted deployments. Since the current instance is already known from the URL, registration, email verification and login already work without ever pressing Connect. From a user's perspective, I'm not sure what purpose the editable server field and the Connect button serve in this scenario. While adding the Caddy configuration would prevent the JavaScript error, it would still leave the same UX question open. I can definitely see this UI making sense for a future generic/official Fluxer client that can connect to arbitrary Fluxer instances, but I'm not sure it makes sense for dedicated self-hosted deployments. Since this issue seems to be a duplicate regarding the JavaScript error, would it make more sense to open a GitHub Discussion (or a separate feature request) to discuss the UX aspect?