We have an env variable called PROXY_TLS_CERTS_PATH. You will need to obtain your TLS certs, place them in a secure folder and set PROXY_TLS_CERTS_PATH to the location of the folder. Note we expect the certs to be named;
cert.pem - Certificate
chain.pem - Certificate Fullchain
privkey.pem - Certificate private key
Take a look at https://letsencrypt.org/ to generate free certificates or see what options your domain host provides.
For the custom domain, your domain host should provide a guide on pointing an A record to the server where Ozone is running,
So, after completing the steps you mentioned (changing env variables), the start-demo process seems to be stuck on the fifth step of the docker build process: RUN apk add curl iproute2 iputils less nano tree ca-certificates lsof --no-cache. It’s been running for 16 minutes, and hasn’t gotten anywhere.
@jack.carney2 the command that times out is a standard Debian command for installing packages. You need to figure out why it times out on your end when you run it in isolation of doing anything with Ozone.
Today I tested the installation again on the fresh server, and I’m still stuck at the same build step.
Maybe because I’m running it on Ubuntu? Would that make a difference? I know apk isn’t a command on Ubuntu.
I ran sudo apt update && sudo apt install curl iproute2 iputils-ping less nano tree ca-certificates lsof outside of Ozone, and then deleted the RUN apk add curl iproute2 iputils less nano tree ca-certificates lsof --no-cache command from the dockerfiles. The installation proceeded without any errors after that.
(As a side note, the SSL cert installed successfully. Thank you. )
@jack.carney2 ideally, this should just work as the steps in the Dockerfile should not be impacted by the host issue. My guess is something is blocking Egress requests out of the host. That is the first place to check. If this worked for you on Gitpod, it should work anywhere else with a well-configured Docker setup.