I have a local installation of Gitlab-ce and I have enabled gitlab-pages using the simplest setup.
Added an A record to point to the server running Gitlab
edited /etc/gitlab/gitlab.rb to contain pages_external_url 'http://gitlab.mydomain.com'
reconfigure
However, when I visit the link after deploying pages I get a 404 page.
What am I doing wrong?
Thanks
Related
I set up a NodeJS API on cPanel using the NodeJS setup that is provided. the app starts but none of my endpoints are reachable with 404 pages being displayed.
In the cPanel > metrics > errors I can see the error: Path for NodeJS application is invalid: /home/username/repositories/repo
where username is the cpanel username and repo is the server.
I used the built in git support in cPanel to link to a remote repo via SSH. This part is most likely not the problem since I can see the actual server files referenced in the NodeJS server with the correct path (which is why this error message is so strange.)
The server works fine on localhost so this likely has something to do with cPanel.
I have never hosted a node app on cPanel and I know a VPS would be better but this is what I have to work with for now. There isn't a lot of discussions/forums/docs on this online so I am running out of options.
I would highly appreciate it if someone can tell me what is wrong or guide me in the right direction for where to start looking for the problem.
I solved the problem. When you don't use a git repo you can use a relative path from your home to the place the server is stored. i.e. don't include home/username/ in the path
for git repos you must use the absolute path meaning
home/username/repositories/yourserver
where "username" is your cPanel username and "yourserver" is the name of the folder where your server is located
I am trying to move a Linux machine from GCP to AWS and its completed. Inside that linux machine, Bitnami ghost blog stack is installed. But while trying to run it from the AWS environment, the URL redirects back to old domain.
I have changed the URL in /opt/bitnami/apps/ghost/htdocs/config.production.json and restarted but this is not working.
Also, I can not see any .htaccess file for redirection
Does any one know how to resolve this redirection issue ?
I am trying to install Gitlab on my newly bought VPS(DigitalOcean, Ubuntu), but after the install and reconfigure, I can't get to the setup page of Gitlab. It's just showing the standard apache not found page. I have changed external_url to -> 'http://myip/gitlab'.
The errors I received after changing the url and reconfigure are below:
Error executing action run on resource 'execute[clear the gitlab-rails cache]'
Error executing action run on resource 'execute[create gitlab database user]'
Error executing action run on resource 'bash[generate assets]'
Error executing action restart on resource 'service[unicorn]'
Error executing action restart on resource 'service[sidekiq]'
Error executing action run on resource 'execute[clear the gitlab-rails cache]'
The Lamp stack is installed, and some basic ufw firewall.
I have used the official Gitlab install/download guide:
https://about.gitlab.com/downloads/#ubuntu1604
Using /gitlab is actually not supported from a omnibus installation. You would need to host it on a (sub)domain.
There is however a way to enable this but it will require quite a significant amount of work to enable GitLab to work like you want. There is quite a extensive tutorial in the GitLab Documentation so I recommend you check that out.
After 5 years, there happened a similar issue. since this one has no accepted answer besides being old, I have given an answer to it that seemingly solved the problem.
If someone finds this post, please check if that solves the issue: installed gitlab on ubuntu shows apache default page
I have recently installed Gitlab on an internal server (192.168.0.XX). After installation I edit the Gitlab.rb file external_ip: 192.168.0.XX and I run the reconfigure file. However when I go to the address on the server I am not served with the Gitlab page. Am I doing something silly?
Don't be an idiot and have Apache running at the same time...
I have installed Gitlab Omnibus gitlab-7.4.3_omnibus.5.1.0.ci-1.el6.x86_64.rpm on CentOS 6.6. I have a few projects created and working fine but I would like to try using the continuous integration features. I don't know where to start and documentation/tutorials are thin on the ground.
I have found the following files that do not appear in an older Gitlab omnibus install I have:
/usr/bin/gitlab-ci-rake
/usr/bin/gitlab-ci-rails
I presume I need to do something with these? But do I need a configuration file first?
In my projects (Settings > Services > Gitlab CI) I can see there are options for Active, Token and Project Url but I do not know what to put in these fields.
Any help to get me started on CI would be appreciated. Cheers,jonny
We recently installed the omnibus GitLab 7.6.2 release which has GitLab CI 5.3 built in. I had the same question. Here's how we got it working.
We're using a single secured server over https; single ip for both gitlab and gitalb-ci hosts.
We have dns entries for both host names to a single ip. (Done with an alias for the ci server I think). We have two ssl certificates one for each hostname.
We have the following lines at the top of the /etc/gitlab/gitlab.rb script (found by searching the gitlab site for rb file setup details):
external_url 'https://gitlab.example.edu'
nginx['redirect_http_to_https'] = true
ci_external_url 'https://gitlab-ci.example.edu'
ci_nginx['redirect_http_to_https'] = true
For http, leave out the nginx statements.
If gitlab-ci url displays the gitlab site contents then the ci_nginx statement needs to be corrected.