Harblet's domain
After the install, Harblet answers at http://<ip>:3000. Give it its own domain, such as harblet.example.com, to reach it over HTTPS.
Set the domain
Point the domain at the first server
Create a DNS A record for the domain with the IP address of your first server.
harblet.example.com. A 203.0.113.10
Upload its certificate
Go to SSL Certificates and upload a certificate that covers the domain. A wildcard certificate for your other domains works too. See Certificates.
Save the domain
Go to Settings → General, enter the domain under Domain and click Save.
Harblet refuses a domain that a service already uses, or one without a valid certificate.
Harblet restarts and is ready a few seconds later at https://harblet.example.com. Log in again there. Your services keep running during the restart.
What changes
- Logins only work at
https://<domain>. Logins at the old address are rejected. - Plain HTTP to the domain is redirected to HTTPS.
- Deploy hook URLs and join commands start with the new domain. Copy the new deploy hook URLs into your pipelines.
- Port 3000 still answers at
http://<ip>:3000for pages, deploy hooks and join commands. Harblet never closes it.
Close port 3000
Once Harblet works at its domain, you can close port 3000 in your firewall. Keep a way to open it again: it's your way back in by IP address if something goes wrong with the domain.
Renew the certificate
Upload the renewed certificate under SSL Certificates before the old one expires. Harblet uses it within seconds. Then delete the old one. Harblet refuses to delete the last valid certificate for its own domain.
Change the domain
Repeat the steps above with the new domain. The old domain stops pointing at Harblet.
Harblet can't go back to its IP address from the browser. If you saved a wrong domain and can't log in, see Troubleshooting.