starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Limit access to different status pages (password restricted) #922

New issue

Closed

opened 2026-02-28 02:03:50 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-28 02:03:50 -05:00

Owner

Originally created by @Sneeex on GitHub (Mar 21, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I would like to be able to set a password for example for status page a and let status page b be public.
(Louislam just made it possible to create multiple pages)

✔️ Solution

It could be using a password or requiring login with the admin account etc.

❓ Alternatives

📝 Additional Context

Originally created by @Sneeex on GitHub (Mar 21, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description I would like to be able to set a password for example for status page a and let status page b be public. (Louislam just made it possible to create multiple pages) ### ✔️ Solution It could be using a password or requiring login with the admin account etc. ### ❓ Alternatives - ### 📝 Additional Context -

deekerman

2026-02-28 02:03:50 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@val123456 commented on GitHub (Mar 23, 2022):

I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-)

@val123456 commented on GitHub (Mar 23, 2022): I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-)

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@Sneeex commented on GitHub (Mar 24, 2022):

I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-)

its a good way but i want it to be implemented into uptime kuma

@Sneeex commented on GitHub (Mar 24, 2022): > I protect various paths (URLs) by using a reverse proxy server in front with basic HTTP auth. Get SSL that way too. :-) its a good way but i want it to be implemented into uptime kuma

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@wrench12435678 commented on GitHub (May 25, 2022):

This would be usefull or at least if you add a domain name, it only is acsessible if coming from that domain.

@wrench12435678 commented on GitHub (May 25, 2022): This would be usefull or at least if you add a domain name, it only is acsessible if coming from that domain.

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@SteffoSpieler commented on GitHub (Dec 8, 2022):

Would be great if it would be possible to set a custom password per status page.

@SteffoSpieler commented on GitHub (Dec 8, 2022): Would be great if it would be possible to set a custom password per status page.

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 3, 2023):

@mathiskir
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1050
If you agree please close this issue, as issue-management is harder with zombies hanging around.
If you disagree, what is the difference?

@CommanderStorm commented on GitHub (Jul 3, 2023): @mathiskir I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1050 If you agree please close this issue, as issue-management is harder with zombies hanging around. If you disagree, what is the difference?

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@vaemarr commented on GitHub (Nov 22, 2023):

I too would like to see this, it's one of the few things actually stopping us from using this with our clients.

@vaemarr commented on GitHub (Nov 22, 2023): I too would like to see this, it's one of the few things actually stopping us from using this with our clients.

deekerman commented

2026-02-28 02:03:57 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 3, 2023):

@mathiskir
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #1050 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 3, 2023): @mathiskir We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1050 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.

deekerman referenced this issue

2026-02-28 02:04:29 -05:00

Race condition in push monitors #937