Erik Zaadi

The tales of a developer with passion for dad jokes

Working with Github from within a company firewall

Most companies with somewhat restricted firewall rules typically enables only web traffic using port 80 or 443 (for SSL).

Git is communicating with Github using port 22 (or the default 9418), which in my own case was blocked after a while.

To keep “gittin” from work there are some options.

  1. Work with pure http access (port 80) git clone This will only give you read only access and is rather slow

  2. Use githubs public server, which works via port 443 git clone ssh://

I use the second one, and it works great, haven’t seen any speed tolls so far.

Reference :



Share on: