Invalid API Key #428

Closed
opened 2026-04-05 16:19:42 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @NANDAKISHORE92 on 7/1/2025

Describe the bug
After upgrading my self hosted OneUptime instance to 7.0.4547, the global Api key doesn't seem to work.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Admin Settings
  2. Click on Settings --> Global Api Key
  3. Enable Master key --> Yes and generate Api key
  4. Use Postman to list monitors using the above generated key, the response in postman says "Invalid API key"

Expected behavior
With the Global Api key, i should be getting success response for all the OneUptime API endpoints.

Screenshots

Image

Image

oneuptime-app pod logs:

Image

Desktop (please complete the following information):

  • OS: Windows
  • Browser Chrome & version 137.0.7151.120
  • OneUptime Version 7.0.4547

Deployment Type
OneUptime deployed in AKS using Helm chart. (Open source Version)

Additional context
I started to see this issue after upgrading from 7.0.4123 to 7.0.4547 only. Although i regenerated the api key couple of times, i still face the same issue. I also ensured the the global api key in OneUptime Admin portal and in my database (Postgres) both are same. I get the same error for all the other endpoints too.

*Originally created by @NANDAKISHORE92 on 7/1/2025* **Describe the bug** After upgrading my self hosted OneUptime instance to **7.0.4547**, the global Api key doesn't seem to work. **To Reproduce** Steps to reproduce the behavior: 1. Go to Admin Settings 2. Click on Settings --> Global Api Key 3. Enable Master key --> Yes and generate Api key 4. Use Postman to list monitors using the above generated key, the response in postman says "Invalid API key" **Expected behavior** With the Global Api key, i should be getting success response for all the OneUptime API endpoints. **Screenshots** ![Image](https://github.com/user-attachments/assets/bd382e4c-3f3d-4ece-b821-08f672e555e4) ![Image](https://github.com/user-attachments/assets/18bcd213-f456-4a26-ab67-4d79e685a285) **oneuptime-app pod logs:** ![Image](https://github.com/user-attachments/assets/c10dbdef-10f3-4a91-97a1-6c58388dd9ca) **Desktop (please complete the following information):** - OS: Windows - Browser Chrome & version 137.0.7151.120 - OneUptime Version 7.0.4547 **Deployment Type** OneUptime deployed in AKS using Helm chart. (Open source Version) **Additional context** I started to see this issue after upgrading from 7.0.4123 to 7.0.4547 only. Although i regenerated the api key couple of times, i still face the same issue. I also ensured the the global api key in OneUptime Admin portal and in my database (Postgres) both are same. I get the same error for all the other endpoints too.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#428