Adds section for Uptime Kuma status pages #661
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Uptime Kuma supports creating status pages. These do not require access to the dashboard (the admin backend), which you might have protected behind authentication. If you've enabled basic auth, LDAP, Authelia, or Authentik, you might want users to be able to reach your status page without having to disable that completely for your entire Uptime Kuma installation.
Benefits of this PR and context
This PR adds a
location
section that allows the status page (and the assets it loads) to bypass any authentication you might have set up.How Has This Been Tested?
Admittedly, my setup is somewhat complicated. I have two servers: one running Unraid 6.12.8 and SWAG (plus the majority of my containers), and another running Ubuntu, Docker, and Uptime Kuma (as the only container). I am using Tailscale to allow SWAG to proxy communication to the Uptime Kuma server, so people can reach my status page without needing access via Tailscale.
I haven't tested this reverse proxy config exactly as-is, since I had to change the
upstream_app
,upstream_port
, andupstream_proto
to accommodate for my setup, but I'm confident that it should work if your SWAG and Uptime Kuma containers are on the same host.Source / References
I'm not great at regex, so I found a Stack Overflow post that gave me enough guidance to figure out how to do this without three additional
location
sections.Also, I'd really appreciate someone making sure I put the curly braces in the right places. I used the Prowlarr config as a reference, as well as the included template.
Thank you for this project, and your continued work to maintain it!