Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds section for Uptime Kuma status pages #661

Merged
merged 1 commit into from
May 25, 2024

Conversation

flammable
Copy link
Contributor

@flammable flammable commented Mar 26, 2024

linuxserver.io


  • [✅] I have read the contributing guideline and understand that I have made the correct modifications

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, and upstream_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!

@Findarato
Copy link
Contributor

Good luck on this, the change looks to work for me.

@drizuid drizuid requested a review from nemchik April 24, 2024 16:23
@LinuxServer-CI
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@nemchik nemchik merged commit d8253f3 into linuxserver:master May 25, 2024
5 checks passed
@flammable
Copy link
Contributor Author

Thank you! 😄

@flammable flammable deleted the uptime-kuma-status-pages branch May 25, 2024 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants