ric/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2024-11-23 23:04:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Updated Reverse Proxy with Cloudflare Tunnel (markdown)

Louis Lam 2022-03-31 00:45:03 +08:00
parent 6eaf7b33e8
commit 38ba1c2cbb
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
Reverse-Proxy-with-Cloudflare-Tunnel.md

@ -1,12 +1,12 @@
## Description
This is the easiest reverse proxy that I have ever seen so far. You don't even need to expose Docker port!
This is the easiest reverse proxy that I have ever seen so far!
Despite a lot of reverse proxy methods in the world, unfortunately, none of them are actually easy-to-use in my opinion. As in the past, many Uptime Kuma users kept asking how to config a reverse proxy.
Recently, I just discovered that Cloudflare has added a web GUI for Cloudflare Tunnel which make it super easy to use. You can expose your Uptime Kuma to the Internet without so many configs!
For Docker users, you just need to provide a Cloudflare Tunnel token in the Settings. Then it is ready to be browsed from the Internet.
For Docker users, you just need to provide a Cloudflare Tunnel token in the Settings, then you can browse Uptime Kuma on the Internet.
Read more about cloudflared:
https://www.reddit.com/r/selfhosted/comments/tp0nqg/cloudflare_has_added_a_web_gui_for_controlling/
@ -15,15 +15,15 @@ Pros:
- Free of charge
- Full GUI, zero-config files
- You can put your Uptime Kuma behind firewall
- No need to expose your real ip
- No need to expose your real IP
- Expose Docker port is optional
- No need nginx, caddy, traefik etc
- No need a reverse proxy software such as Nginx, Caddy or Traefik
- Zero-config SSL
- Free SSL
Cons:
- (Not a con if you are already using Cloudflare) You domain's nameserver have to move to Cloudflare.
- add 30MB to the docker base image
- Added 30MB to the docker base image
## Requirements
@ -43,7 +43,7 @@ Cons:
The steps are actually very simple. However, since the concept is pretty new to anyone, it may be good to write it in detail.
But trust me, once you learnt, you will remember how to config without this guide again! While for nginx, Traefik, I never could remember how to config without googling it.
But trust me, once you learnt, you will remember how to config without this guide again! While for Nginx or Traefik, I never could remember how to config without googling it.
@ -88,7 +88,7 @@ But trust me, once you learnt, you will remember how to config without this guid
Alternatively, you can set the token via a environment variable. cloudflared will be started automatically.
With this approach, you don't even need to expose your container port to host machine.
With this approach, you don't even need to expose your container port to the host machine.
UPTIME_KUMA_CLOUDFLARED_TOKEN=`<your token>`