Updated TLS (markdown)

Christian Mäder 2021-01-22 11:38:46 +01:00
parent 9b326e8991
commit 3abd9515cf

13
TLS.md

@ -29,8 +29,8 @@ Continue with [TLS Using Hitch](#tls-using-hitch).
## TLS for the world
In order to setup TLS to serve public traffic to your Netbox it is recommended to set up a reverse proxy that is independent from Netbox.
You can do this by installing a webserver like _nginx_ on your host machine directly or by running it in a container.
But we advise against changing the nginx configuration that ships with Netbox Docker.
You can do this by installing a webserver like _nginx_ on your host machine directly or by running it in a container, [as explained below with _Hitch_](#tls-using-hitch).
But we strongly advise against changing the Nginx configuration that ships with Netbox Docker.
### TLS Using Hitch
@ -64,4 +64,11 @@ services:
- 8443:443 # bind the container's port 443 to the host's port 8443 -> https://[::1]:8443
```
> NOTE: From **version 0.28.0** and above the `nginx` service is no longer in use. The traffic must be forwarded to the netbox service directly.
> **NOTE:**
>
> Starting with Netbox Docker **0.28.0**, the `nginx` service is no longer in use. The traffic must be forwarded to the `netbox` service directly:
>
> ```patch
> - HITCH_PARAMS: --backend=[nginx]:8080 --frontend=[*]:443 # listen on *:443 and forward traffic to nginx:8080
> + HITCH_PARAMS: --backend=[netbox]:8080 --frontend=[*]:443 # listen on *:443 and forward traffic to netbox:8080
> ```