History

Reformat docs (#13897)

Patrick Schratz committed 5 years ago

Commit af796771 parent 97ab82086 files · +1128 −970Browse files

Showing the changes to docs/content/doc/usage/https-support.md (1 of 86 files). Show all

Unified · Split

docs/content/doc/usage/https-support.md+10−5
@@ -3,7 +3,7 @@ date: "2018-06-02T11:00:00+02:00" · 2 unmodified lines
3title: "Usage: HTTPS setup"3title: "Usage: HTTPS setup"
4slug: "https-setup"4slug: "https-setup"
5weight: 125weight: 12
6toc: true6toc: false
7draft: false7draft: false
8menu:8menu:
9 sidebar:9 sidebar:
@@ -15,6 +15,10 @@ menu: · 5 unmodified lines
15 15
16# HTTPS setup to encrypt connections to Gitea16# HTTPS setup to encrypt connections to Gitea
17 17
18**Table of Contents**
19
20{{< toc >}}
21
18## Using the built-in server22## Using the built-in server
19 23
20Before you enable HTTPS, make sure that you have valid SSL/TLS certificates.24Before you enable HTTPS, make sure that you have valid SSL/TLS certificates.
@@ -32,6 +36,7 @@ HTTP_PORT = 3000 · 11 unmodified lines
32CERT_FILE = cert.pem36CERT_FILE = cert.pem
33KEY_FILE = key.pem37KEY_FILE = key.pem
34```38```
39
35Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship.40Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship.
36To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).41To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).
37 42
@@ -66,14 +71,14 @@ LETSENCRYPT_EMAIL=email@example.com · 28 unmodified lines
66 71
67To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).72To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).
68 73
69## Using reverse proxy74## Using a reverse proxy
70 75
71Setup up your reverse proxy as shown in the [reverse proxy guide](../reverse-proxies).76Setup up your reverse proxy as shown in the [reverse proxy guide](../reverse-proxies).
72 77
73After that, enable HTTPS by following one of these guides:78After that, enable HTTPS by following one of these guides:
74 79
75* [nginx](https://nginx.org/en/docs/http/configuring_https_servers.html)80- [nginx](https://nginx.org/en/docs/http/configuring_https_servers.html)
76* [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html)81- [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html)
77* [caddy](https://caddyserver.com/docs/tls)82- [caddy](https://caddyserver.com/docs/tls)
78 83
79Note: Enabling HTTPS only at the proxy level is referred as [TLS Termination Proxy](https://en.wikipedia.org/wiki/TLS_termination_proxy). The proxy server accepts incoming TLS connections, decrypts the contents, and passes the now unencrypted contents to Gitea. This is normally fine as long as both the proxy and Gitea instances are either on the same machine, or on different machines within private network (with the proxy is exposed to outside network). If your Gitea instance is separated from your proxy over a public network, or if you want full end-to-end encryption, you can also [enable HTTPS support directly in Gitea using built-in server](#using-the-built-in-server) and forward the connections over HTTPS instead.84Note: Enabling HTTPS only at the proxy level is referred as [TLS Termination Proxy](https://en.wikipedia.org/wiki/TLS_termination_proxy). The proxy server accepts incoming TLS connections, decrypts the contents, and passes the now unencrypted contents to Gitea. This is normally fine as long as both the proxy and Gitea instances are either on the same machine, or on different machines within private network (with the proxy is exposed to outside network). If your Gitea instance is separated from your proxy over a public network, or if you want full end-to-end encryption, you can also [enable HTTPS support directly in Gitea using built-in server](#using-the-built-in-server) and forward the connections over HTTPS instead.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t