Im pissed…
Installed GitLab CE by following guide on webpage. Everything is fine but when I point my browser to where GL is listening I end up with blank page.
My OS is CentOS 7.3
Any help?
NO HELP ? Really bad
Which install guide did you follow? There are different ways to install each would have different next steps to troubleshoot the issue.
I was following this guide…
Okay. Start by confirming all the gitlab services are running.
$ sudo gitlab-ctl status
run: gitlab-workhorse: (pid 16055) 1555095s; run: log: (pid 652) 7926213s
run: logrotate: (pid 31120) 3354s; run: log: (pid 668) 7926213s
run: nginx: (pid 16068) 1555094s; run: log: (pid 654) 7926213s
run: postgresql: (pid 15481) 1555161s; run: log: (pid 659) 7926213s
run: redis: (pid 15489) 1555161s; run: log: (pid 657) 7926213s
run: registry: (pid 16076) 1555093s; run: log: (pid 675) 7926213s
run: sidekiq: (pid 16044) 1555099s; run: log: (pid 650) 7926213s
run: unicorn: (pid 16083) 1555093s; run: log: (pid 661) 7926213s
If everything appears to be running check the rails log for errors when you open the site in your browser.
$ sudo tail -f /var/log/gitlab/gitlab-rails/production.log
And if you don’t see any log messages that correspond to your attempts to load the page in your browser, double-check the firewall is open for http
$ sudo firewall-cmd --list-services
And if after all of this you can’t determine what’s wrong you can try setting the external URL
1 Like
sudo gitlab-ctl status
run: gitlab-workhorse: (pid 16055) 1555095s; run: log: (pid 652) 7926213s
run: logrotate: (pid 31120) 3354s; run: log: (pid 668) 7926213s
run: nginx: (pid 16068) 1555094s; run: log: (pid 654) 7926213s
run: postgresql: (pid 15481) 1555161s; run: log: (pid 659) 7926213s
run: redis: (pid 15489) 1555161s; run: log: (pid 657) 7926213s
run: registry: (pid 16076) 1555093s; run: log: (pid 675) 7926213s
run: sidekiq: (pid 16044) 1555099s; run: log: (pid 650) 7926213s
run: unicorn: (pid 16083) 1555093s; run: log: (pid 661) 7926213sNO EXTERNAL ADDR
I want normal one.
My guess is that you should turn the built in centos firewall off, and if that works, then turn it back on, and configure your firewall rules on Centos.
No matter what the state of fw (on or off) is, GitLab’s main page is inaccessible.
I’m just a user like you, not a representative of GitLab. I was willing to try to help you, despite your tone, and asked you to do some basic troubleshooting. I’m not sure what you hope to gain by shouting and calling names but It won’t be any more help from me and my free time.
I get the impression that you think you are owed something even when using a free product. You should consider paying for the product and then you will have access to the professional support of the company that makes the free product.
4 Likes
to make free product and then require paymenbt in return of support its unfair, and against GPL licence. GitLab is free and based on GPL. Its simply fraud.
GitLab is MIT licensed, not GPL.
3 Likes
Welcome to Gitlab,
GitLab is free, unlike Github. If you don’t like it make your own Git server. You really have nothing to
complain about.
Obviously, the function works you’re just doing it wrong. Because you’re a fucking noob.
And you’re obviously a cheapskate and your username confirms that.
They can obviously charge money for support, you think people will just help you for free? are you helping for free? Well… not that you have the knowledge to help anyone… But still.
FYI: My username is name of my phone + last two digits of year I got it (2011).
Hi
May be people don’t like the way you are talking. Please let me know if you are able to access the web page or you are still facing the issue. I just want to help you out of interest.
1 Like
Im not talkingb the way I talk here normally; Im talking in rude tone, because Im pissed (I tried to switch my code hosting from GitHub to GitLab and - due to some crazy bugs in GL - I wasnt succesfull). In fact - while trying to install GitLab - I broke my production environment (on test env it was all ok). And I ended up here (in GL support forum and in issues. On issues I was ignored. Thats why Im pissed.
Answering your question - I still am unable to acces my own instance of GitLab.
There’s a difference between rude and abusive. Just like there’s a difference between production and testing. The fact that you messed up your production environment by trying to install gitlab isn’t on gitlab or this community. That’s on you.
Wrong.
Its GitLab’s developer’s whose obligation is to provide working ways of installing their software. Period.
In my experience the omnibus installation worked flawlessly. More than once. A double for every upgrade since the initial install. Of course initially this was not done on a new server so as not to disturb production.
It is your obligation to try new software out in a separate environment so you don’t mess up your primary. Placing the blame elsewhere is misguided and clearly not effective since you are still raging about it.
I (=we) have been testing GitLab on our test enviroment for 2+ weeks, and it worked.