The logs were clean until the network call froze. The cause wasn’t the code. It was the port. Port 8443. And it was blocking your Git checkout.
Port 8443 is often used for secure web services running over HTTPS. If you’re trying to run git checkout against a repository served over HTTPS on a non-default port, a few things can happen. Firewall rules might block the connection. Corporate proxies might refuse traffic outside 443. Security groups in your cloud configuration may not allow ingress or egress on 8443 by default.
To debug, first confirm connectivity. A simple curl -v https://your-domain:8443 will show if the handshake succeeds. If it fails, narrow down the issue. If you are behind a corporate firewall or a VPN, check with your network policy. If you are running in a CI/CD pipeline, look at the container or VM’s outbound rules.
Git itself doesn’t care about ports. It follows the URL. But your environment does. For self-hosted Git services or certain DevOps tools, 8443 may be the default for API and web UI access. When you run: