upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor synced 2025-04-13 13:51:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8395 from alexander-lloyd/master

Browse Source 
Fix typo in https configuration docs
This commit is contained in:
Qian Deng 2019-08-27 18:29:26 +08:00 committed by GitHub
commit 8e5ea7bdc5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/configure_https.md
View File

@ -155,7 +155,7 @@ After setting up HTTPS for Harbor, you can verify it by the following steps:
* Notice that some browser may still shows the warning regarding Certificate Authority (CA) unknown for security reason even though we signed certificates by self-signed CA and deploy the CA to the place mentioned above. It is because self-signed CA essentially is not a trusted third-party CA. You can import the CA to the browser on your own to solve the warning.
* On a machine with Docker daemon, make sure the option "-insecure-registry" for https://yourdomain.com does not present.
* On a machine with Docker daemon, make sure the option "-insecure-registry" for https://yourdomain.com is not present.
* If you mapped nginx port 443 to another port, then you should instead create the directory ```/etc/docker/certs.d/yourdomain.com:port``` (or your registry host IP:port). Then run any docker command to verify the setup, e.g.