Skip to content

Commit

Permalink
Merge pull request goharbor#2318 from timchenxiaoyu/timchenxiaoyu-pat…
Browse files Browse the repository at this point in the history
…ch-1

docs error
  • Loading branch information
reasonerjt authored Aug 4, 2017
2 parents 65a19b4 + 86062d9 commit ef909b4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/configure_https.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,8 @@ After setting up HTTPS for Harbor, you can verify it by the following steps:

1. Open a browser and enter the address: https://reg.yourdomain.com . It should display the user interface of Harbor.

2. On a machine with Docker daemon, make sure the option "-insecure-registry" does not present, and you must copy ca.crt generated in the above step to /etc/docker/certs.d/yourdomain.com(or your registry host IP), if the directory does not exist, create it.
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.
2. On a machine with Docker daemon, make sure the option "-insecure-registry" does not present, and you must copy ca.crt generated in the above step to /etc/docker/certs.d/reg.yourdomain.com(or your registry host IP), if the directory does not exist, create it.
If you mapped nginx port 443 to another port, then you should instead create the directory /etc/docker/certs.d/reg.yourdomain.com:port(or your registry host IP:port). Then run any docker command to verify the setup, e.g.

```
docker login reg.yourdomain.com
Expand Down

0 comments on commit ef909b4

Please sign in to comment.