Allow a user configurable push URL instead of randomly generated hash. #2580

New issue

Open

opened 2026-02-28 02:59:41 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-28 02:59:41 -05:00

Owner

Originally created by @shivaneshlal on GitHub (Sep 13, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

As Uptime Kuma's user base expands, there's an increasing need for flexibility in how we deploy and maintain scripts for multiple instances. One area where this flexibility can greatly benefit users is in the push URL.

Currently, Uptime Kuma generates a randomly hashed push URL which, while secure, can pose challenges for automated deployments and scripts across various instances. By allowing users to define custom parameters in the push URL instead of solely relying on the randomly generated hash.

For those who use automation tools or scripts to deploy multiple instances, having a predictable or user-defined URL can significantly streamline the process.
If users can define their parameters, they can create naming conventions or structures that make sense for their specific use case, making it easier to manage and identify individual instances.
Custom parameters can aid in better integration with third-party tools and platforms, as users can ensure that URL structures align with other systems they're using.

✔️ Solution

We believe this enhancement will improve user experience, especially for power users and those managing multiple Uptime Kuma instances. While security is paramount and the randomly generated hash serves an important purpose, providing the option for custom parameters can offer both security and convenience when done correctly.

We hope to see this feature in the upcoming releases of Uptime Kuma.

Thank you for considering this request!

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @shivaneshlal on GitHub (Sep 13, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description As Uptime Kuma's user base expands, there's an increasing need for flexibility in how we deploy and maintain scripts for multiple instances. One area where this flexibility can greatly benefit users is in the push URL. Currently, Uptime Kuma generates a randomly hashed push URL which, while secure, can pose challenges for automated deployments and scripts across various instances. By allowing users to define custom parameters in the push URL instead of solely relying on the randomly generated hash. For those who use automation tools or scripts to deploy multiple instances, having a predictable or user-defined URL can significantly streamline the process. If users can define their parameters, they can create naming conventions or structures that make sense for their specific use case, making it easier to manage and identify individual instances. Custom parameters can aid in better integration with third-party tools and platforms, as users can ensure that URL structures align with other systems they're using. ### ✔️ Solution We believe this enhancement will improve user experience, especially for power users and those managing multiple Uptime Kuma instances. While security is paramount and the randomly generated hash serves an important purpose, providing the option for custom parameters can offer both security and convenience when done correctly. We hope to see this feature in the upcoming releases of Uptime Kuma. Thank you for considering this request! ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_