CODEWITHSUNDEEP
gitlab
niren
niren

Reputation: 2731

gitlab is inaccessible from browser

After sudden restart of server, gitlab is inaccessible. I don't know whats happen. I have posted another question as well check this here. Gitlab is up and running when I start/restart from server but it is inaccessible from browser(This is way I used to access GtiLab).

When I start GitLab

The GitLab Unicorn web server with pid 2020 is running
The GitLab SideKiq job dispatcher with pid 2028 is running
GitLab and all its components are up and running.

but I can't access the web interface of gitlab by using IP of Git container: 192.168.2.9. I can able to ping 192.168.2.9 from my system.

Upvotes: 4

Views: 9055

Answers (2)

Ruxandra T.
Ruxandra T.

Reputation: 531

I had this problem after the restart of the machine. It turned out that I had installed a firewall that was re-enabled at startup, so the connection would be refused. I disabled it and all worked fine afterwards.

Upvotes: 0

BostAxola
BostAxola

Reputation: 66

That you can ping 192.168.2.9 does nothing to do with GitLab page not showing up. First of all, it would we helpful if you could paste the output of this commands:

sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
sudo -u git -H /home/git/gitlab-shell/bin/check

You can also check GitLab's & nginx's logs for errors and that you configured well GitLab's page on nginx.

If you keep finding troubles I recommend you to Install the lates Omnibus version at: https://www.gitlab.com/downloads/ which will install you the latest GitLab stable version and all it's dependencies, so you don't have to do a manual installation.

Upvotes: 1

Related Questions