docs: Also mention changing the HTTP port for permissions errors

This commit is contained in:
Matthew Holt 2020-04-08 13:41:18 -06:00
parent d3a35d67e8
commit 632345845c
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
2 changed files with 4 additions and 4 deletions

View file

@ -13,7 +13,7 @@ localhost
```
<aside class="tip">
If the HTTP and HTTPS ports (80 and 443, respectively) are privileged ports on your OS, you will either need to run with elevated privileges or use a higher port. To use a higher port, just change the address to something like <code>localhost:2015</code>. You'll still get HTTPS unless you turn it off.
If the HTTP and HTTPS ports (80 and 443, respectively) are privileged ports on your OS, you will either need to run with elevated privileges or use a higher port. To use a higher port, just change the address to something like <code>localhost:2015</code> and change the HTTP port using the <a href="/docs/caddyfile/options">http_port</a> Caddyfile option.
</aside>
Then hit enter and type what you want it to do, so it looks like this:
@ -34,7 +34,7 @@ You will probably be asked for your password, because Caddy serves all sites --
For local HTTPS, Caddy automatically generates certificates and unique private keys for you. The root certificate is added to your system's trust store, which is why the password prompt is necessary. It allows you to develop locally over HTTPS without certificate errors.
</aside>
If you get permission errors, you may need to run with elevated privileges or use a higher port; a quick fix is to change your site's address to `localhost:2015` or similar.
If you get permission errors, you may need to run with elevated privileges.
Either open your browser to [localhost](http://localhost) or `curl` it: