GitLab.com now supports an alternate git+ssh port

When encountering the "port 22: Connection refused" error while pushing changes to GitLab, users can now utilize an alternate SSH port (443) on GitLab.com to bypass network restrictions that block the standard SSH port. This is particularly beneficial in environments where only ports 80 and 443 are allowed due to firewall rules. GitLab has implemented a solution using Azure and HAProxy to forward connections from port 443 to port 22, thereby enabling users to connect via a commonly open port without requiring significant configuration changes. To use this alternate SSH connection, users must modify their SSH configuration file by specifying the hostname altssh.gitlab.com and port 443. Upon first connection, users will need to verify the server’s key fingerprint, which matches that of GitLab.com. This setup provides a seamless way to maintain GitLab connectivity without relying on potentially blocked tools like VPNs or more complex network configurations.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.