Forked from arastu/create-cert-and-key-with-certbot.sh
Last active
January 15, 2021 09:07
-
-
Save beevelop/4ba8692d99f5af8604560ecae92be38f to your computer and use it in GitHub Desktop.
Configuring Harbor with HTTPS Access via letsencrypt(certbot with --standalone flag)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sudo certbot -d reg.example.com --manual --preferred-challenges dns certonly |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#The IP address or hostname to access admin UI and registry service. | |
#DO NOT use localhost or 127.0.0.1, because Harbor needs to be accessed by external clients. | |
hostname = registry.example.com | |
#The protocol for accessing the UI and token/notification service, by default it is http. | |
#It can be set to https if ssl is enabled on nginx. | |
ui_url_protocol = https | |
#The path of cert and key files for nginx, they are applied only the protocol is set to https | |
ssl_cert = /etc/letsencrypt/live/registry.example.com/fullchain.pem | |
ssl_cert_key = /etc/letsencrypt/live/registry.example.com/privkey.pem |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment