title: I can only connect to my GitLab server from a remote network
body: <p>Yesterday at work, I had been happily using my brand new GitLab server (which was back at my house) all day. Pushing, pulling, and merging all worked just fine. When I got home, I wanted to touch up a personal project, but when I tried to pull the repo from my server, I got this message:</p>
  
  <p><code>fatal: unable to access 'http://git.ghostlyco.de/revxx14/new-site.git/': Failed connect to git.ghostlyco.de:80; No error</code></p>
  
  <p>I thought "Hmm, that's odd. I've been connecting just fine all day." So I tried it a few more times, and got the same error. I tried using the IP address instead of the domain, same deal. Local IP address, exactly the same thing. I tried it on another account on the computer, and got the same error. I tried it on a completely different computer, and got the same error. I tried switching from wired internet to wireless, same deal. I tried rebooting my machine, and yep, same issue. I tried rebooting the server, to no avail.</p>
  
  <p>I went to bed frustrated, I had no idea what could be happening. I can pull up the site just fine in my browser, which added to the confusion. </p>
  
  <p>When I woke up this morning, I had one last idea I could try: a completely different connection. I figured that's the only other difference I had when connecting from work. So I set up internet tethering on my phone, pulled the repo, and...SUCCESS!</p>
  
  <p>So apparently I can't connect to my GitLab server if I'm on the same network. This is blowing my mind. I definitely understand why I wouldn't be able to connect  remotely if I didn't set up port forwarding properly, but within the local network? This makes no sense.</p>
  
  <p>I'm not a networking or command line guy, so I have no idea where to start to look in to this. Any help would be greatly appreciated.</p>
  
  <p>FYI I'm running GitLab on a Ubuntu 12.04 LTS x86 server, if that makes a difference.</p>
  
  <hr>
  
  <p>EDIT: Apparently the local IP is now working. I guess that's fine? This is so weird. No idea why it can't connect to the IP address/domain.</p>