#Cloudflare zero trust ssh how to#
#Cloudflare zero trust ssh password#

Navigate to the Cloudflared Configuration file location Navigate over to the Cloudflared configuration file cd /etc/cloudflared Let's go in and edit the cloudflared configuration file.

#Cloudflare zero trust ssh how to#

This section of the tutorial assumes that you've configured Cloudflared as a service on your VPS, check out how to configure Cloudflared on Cloudflare or check out my previous blog around setting up Cloudflared for a secure Ghost blog Mkdir data Bash commands to create the folder structure I use to manage host-to-container volumes for Docker Composeīefore we spin up the Gitlab service let's configure Cloudflared and Cloudflare's DNS settings for our website. (Note: you may need to use Sudo here if it throws a permission error, it's entirely dependent on how you've setup and configured your users on your VPS): To do this yourself execute the following commands line by line. For me, Under my /home/username/ folder I've created a folder called 'stack_volumes/GitLab/ and duplicated the 3 folders - Config, Data and Logs. Depending on how you have set up your VPS your approach to storing data from containers may differ. There are three primary Volumes that we need to map to the host from the container for Gitlab to use.It's worth pointing out the reason why we're mapping 2224 as opposed to 22 to port 22 in the container is that I'm running ssh through cloudflared to my VPS. This port enables you to git push to your own Gitlab instance. Port 2224:22 maps an external port of 2224 to port 22 for ssh. We're mapping several Ports here 80:80 tells Docker to spin up the web interface on port 80 - this works for us as we don't need to deploy over HTTPS as our Cloudflared setup covers us for this.

#Cloudflare zero trust ssh password#

The Environment contains the initial root password that's required to login to the Gitlab web interface as the latest version of Gitlab prevents additional user signup without administrator approval forcing us to have to set this when we deploy the container.

The image tells Docker that we want to pull the latest Gitlab/Gitlab-ee image.

We're setting the hostname as the URL that you'll end up browsing to.

Let's break down the Docker Compose file so we understand what's inside: I've included the docker-compose.yml file below to make it easier 👇 '/home//stack_volumes/gitlab/data:/var/opt/gitlab' Gitlab Docker Compose file

'/home//stack_volumes/gitlab/logs:/var/log/gitlab' '/home//stack_volumes/gitlab/config:/etc/gitlab'

In the docker-compose.yml file use the following YAML to define the service we want to deploy version: '3.7' Nano docker-compose.yml Create the folder to house the Docker-compose file This tutorial assumes that you've already installed Docker and Docker compose on your VPS.įirst, let's create the Docker-compose file that will spin up our service -I like to put all my docker containers in the same folder. Configuring Cloudflared and protecting your Gitlab instance using Cloudflare Access on Cloudflare's Zero Trust platform Deploy GitLab on Docker with Docker Compose Learn how to self-host Gitlab on your own private VPS using Docker and Docker Compose. This guide assumes you already have a VPS setup and running and a Domain already set up on Cloudflare.