Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

GitLab Error: – GitLab is not responding

Spread the Knowledge

rajeshkumar created the topic: GitLab is not responding
Issues –
After setting up the gitlab in ubantu by following…n-local-machine.html

I am getting error called “GitLab is not responding” on front page.

Followup –

I did run status commands and got following output…

sudo gitlab-ctl status
run: nginx: (pid 12728) 165s; run: log: (pid 12574) 372s
run: postgresql: (pid 12731) 165s; run: log: (pid 12485) 421s
run: redis: (pid 12741) 165s; run: log: (pid 12402) 427s
run: sidekiq: (pid 12744) 165s; run: log: (pid 12558) 378s
run: unicorn: (pid 12808) 28s; run: log: (pid 12546) 380s

I stop and restart the gitlab using…

sudo gitlab-ctl start
ok: run: nginx: (pid 12961) 0s
ok: run: postgresql: (pid 12964) 0s
ok: run: redis: (pid 12967) 0s
ok: run: sidekiq: (pid 12970) 0s
ok: run: unicorn: (pid 12983) 0s


I found out that some other services was running with port 80. I just stopped that services and re-startted the gitlab services and it went through..
Rajesh Kumar
Twitt me @

Rajesh Kumar
0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x