Gitlab 502 bad gateway

January 2, 2014 12.7k views
f.heppell
By:
f.heppell
I'm trying to follow the gitlab and have properly configured it (the domain is my droplet's ip, that should be ok, right?). I've started the server and I'm getting a 502 bad gateway area. In addition to that the command line displays 'master failed to start, check stderr log for details'. Why is this?
Log In to Comment
3 Answers
f.heppell January 3, 2014
Anybody know? This is quite annoying!
Reply
f.heppell January 3, 2014
Okay, this issue has been fixed.
See this article (troubleshooting section) https://www.digitalocean.com/community/articles/how-to-set-up-gitlab-as-your-very-own-private-github-clone
How To Set Up GitLab As Your Very Own Private GitHub Clone
by Nik van der Ploeg
GitLab provides a simple but powerful web based interface to your Git repositories a la GitHub. Only you can host it on your own cloud server, control access as you see fit, and repo size is limited only by how much storage space your server has. This tutorial will walk you through setting up a DigitalOcean VPS as a GitLab server.
Reply
FranciscoRaulOrtega February 23, 2014
I fixed the 502 , however I'm getting a 500 bad gateway. I post a new question on the forum here. thanks
Reply
Have another answer? Share your knowledge.