Updated Reverse Proxy (markdown)

master
Louis Lam 4 years ago
parent
commit
c6c228169c
  1. 33
      Reverse-Proxy.md

33
Reverse-Proxy.md

@ -9,9 +9,10 @@ Uptime Kuma **do not supported on subdirectory** reverse proxy. Please prepare a
- [Caddy](#caddy) - [Caddy](#caddy)
- [Nginx Proxy Manager](#nginx-proxy-manager) - [Nginx Proxy Manager](#nginx-proxy-manager)
- [Synology Builtin Reverse Proxy](#synology-builtin-reverse-proxy) - [Synology Builtin Reverse Proxy](#synology-builtin-reverse-proxy)
- [Cloudflare](#cloudflare)
- [SSL/HTTPS](#ssl-https)
- [Traefik](#Traefik) - [Traefik](#Traefik)
- [Cloudflare](#cloudflare)
- Others
- [SSL/HTTPS](#sslhttps)
# Nginx # Nginx
@ -100,6 +101,18 @@ Please enable "WebSockets Supports"
https://mlohr.com/websockets-for-synology-dsm/ https://mlohr.com/websockets-for-synology-dsm/
# Traefik
```
labels:
- "traefik.enable=true"
- "traefik.http.routers.uptime-kuma.rule=Host(`YourOwnHostname`)"
- "traefik.http.routers.uptime-kuma.entrypoints=https"
- "traefik.http.routers.uptime-kuma.tls=true"
- "traefik.http.routers.uptime-kuma.tls.certresolver=myresolver"
- "traefik.http.services.uptime-kuma.loadBalancer.server.port=3001"
```
Add the above, to your Docker-compose.yml file, and replace "YourOwnHostname" with the hostname you want to use, to use Traefik reverse Proxy. Note setup correct, Traefik can automaticly, get a Let's Encrypt certificate for your service.
# Cloudflare # Cloudflare
You must enable "WebSockets" in Cloudflare Dashboard: You must enable "WebSockets" in Cloudflare Dashboard:
@ -109,22 +122,10 @@ Cloudflare Dashboard -> Network -> Enable WebSockets
Read more: Read more:
https://github.com/louislam/uptime-kuma/issues/138#issuecomment-890485229 https://github.com/louislam/uptime-kuma/issues/138#issuecomment-890485229
# Others
# SSL/HTTPS ## SSL/HTTPS
It is recommended to use SSL(HTTPS) with your web-server to avoid MiTM attacks when on a public network. If using caddy these certificates will be auto-generated by caddy and will keep them updated. It is recommended to use SSL(HTTPS) with your web-server to avoid MiTM attacks when on a public network. If using caddy these certificates will be auto-generated by caddy and will keep them updated.
If your using Apache or NGINX, it is recommended to use CertBot to manage SSL for free, it uses Let's Encrypt to get it's certificates and keeps them renewed. You can also use your own Certificates and place them as shown above. If using cerbot use the "Without SSL" settings and then run certbot on it and it will automatically configure auto-HTTPS redirection. If your using Apache or NGINX, it is recommended to use CertBot to manage SSL for free, it uses Let's Encrypt to get it's certificates and keeps them renewed. You can also use your own Certificates and place them as shown above. If using cerbot use the "Without SSL" settings and then run certbot on it and it will automatically configure auto-HTTPS redirection.
# Traefik
```
labels:
- "traefik.enable=true"
- "traefik.http.routers.uptime-kuma.rule=Host(`YourOwnHostname`)"
- "traefik.http.routers.uptime-kuma.entrypoints=https"
- "traefik.http.routers.uptime-kuma.tls=true"
- "traefik.http.routers.uptime-kuma.tls.certresolver=myresolver"
- "traefik.http.services.uptime-kuma.loadBalancer.server.port=3001"
```
Add the above, to your Docker-compose.yml file, and replace "YourOwnHostname" with the hostname you want to use, to use Traefik reverse Proxy. Note setup correct, Traefik can automaticly, get a Let's Encrypt certificate for your service.

Loading…
Cancel
Save