Latest news about Bitcoin and all cryptocurrencies. Your daily crypto news habit.
This is a final post just in case something went wrong with your GitLab installation:
Posts:
- [TutorialāāāGuide] Installing GitLab, GitLab CI on AWS EC2 fromĀ Zero.
- Configure GitLab CI on AWS EC2 UsingĀ Docker
- ConfiguringĀ .gitlab-ci.yml
- Troubleshooting GitLab and GitLab CI (ThisĀ Post)
#1-IP Changed on GitLab RepoāāāDisplaying wrongĀ URL
You forgot to set an Elastic IP, the IP changed and now your project changed, and now GitLab doesnāt know how to work itĀ out.
We need to change the external URL from the /etc/gitlab/gitlab.rb file:
#Alternative 1āāāChange it usingĀ Vim
(Go to your PuTTY terminal, andĀ run:
sudo vim /etc/gitlab/gitlab.rb
Press the letter āiā to startĀ editing.
Check line 13. Thatās ourĀ culprit.
After you finish editing, press esc and typeĀ :wq This will write and quit theĀ program.
#Alternative 2ā Download the file and change itsĀ content.
Alternatively, you can access the file directly through FTP via Filezilla or WinSCP. But youāre going to have to temporarily enable access of theĀ file:
sudo chmod 777 /etc/gitlab/gitlab.rb
From <https://forum.filezilla-project.org/viewtopic.php?t=22618>
After that, weāre able to download the file and editĀ it:
Change Line 13. Reupload the file to save theĀ changes.
Donāt forget toĀ run:
sudo chmod 600 /etc/gitlab/gitlab.rb
For all alternatives, run:
sudo gitlab-ctl reconfigure
For changes to takeĀ effect.
Remember to set an Elastic IP in AWS so this doesnātā happenĀ again!
#2- What to do in case the project build or any other stage isĀ failing:
- In case you receive that No task runners are running. Then, that couldĀ mean:
- The task runner is not running. Use sudo gitlab-runner start OR sudo gitlab-runner run to make itĀ work.
- The task runner is configured to run with tags and your job doesnāt have tags with it! Tags arenāt set at the project level, but at the job level inside theĀ .gitlab-ci.yml file!
2. In case that you receive a connection time outĀ problem
In this specific case, the problem was with the lack Elastic IP, and the server address change. By not using Elastic IP, your serverās address is releasedĀ , and is completely changed.
Troubleshooting GitLab and GitLab CI was originally published in Hacker Noon on Medium, where people are continuing the conversation by highlighting and responding to this story.
Disclaimer
The views and opinions expressed in this article are solely those of the authors and do not reflect the views of Bitcoin Insider. Every investment and trading move involves risk - this is especially true for cryptocurrencies given their volatility. We strongly advise our readers to conduct their own research when making a decision.