OpsGenie notification broken #3965

Open
opened 2026-02-28 03:46:36 -05:00 by deekerman · 1 comment
Owner

Originally created by @d11ahirst on GitHub (Feb 11, 2025).

None

🛡️ Security Policy

Description

When using the OpsGenie notification we recieve a 403 from the opsgenie service despite generating a new API key and giving it full permissions. This was done in the EU region

👟 Reproduction steps

Create an OpsGenie notification fill in the correct fields

Notification Type: OpsGenie
Friendly Name: test
Region: EU
API Key: Generated from the OpsGenie Settings API Keys Page.
Priority 2

Click Test

👀 Expected behavior

Successful notification is sent

😓 Actual Behavior

403 error

🐻 Uptime-Kuma Version

Beta 2.01

💻 Operating System and Arch

Amazon Linux

🌐 Browser

Chrome

🖥️ Deployment Environment

  • Runtime: Docker
  • Database: Sql Lite
  • Filesystem used to store the database on: ext4
  • number of monitors: 1

📝 Relevant log output

status: 403,
 statusText: 'Forbidden',
Originally created by @d11ahirst on GitHub (Feb 11, 2025). ### 📑 I have found these related issues/pull requests None ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description When using the OpsGenie notification we recieve a 403 from the opsgenie service despite generating a new API key and giving it full permissions. This was done in the EU region ### 👟 Reproduction steps Create an OpsGenie notification fill in the correct fields Notification Type: **OpsGenie** Friendly Name: **test** Region: **EU** API Key: **Generated from the OpsGenie Settings API Keys Page.** Priority **2** Click **Test** ### 👀 Expected behavior Successful notification is sent ### 😓 Actual Behavior 403 error ### 🐻 Uptime-Kuma Version Beta 2.01 ### 💻 Operating System and Arch Amazon Linux ### 🌐 Browser Chrome ### 🖥️ Deployment Environment - Runtime: Docker - Database: Sql Lite - Filesystem used to store the database on: ext4 - number of monitors: 1 ### 📝 Relevant log output ```shell status: 403, statusText: 'Forbidden', ```
Author
Owner

@CommanderStorm commented on GitHub (Apr 17, 2025):

we maintainers don't have time to track down bugs in notification providers given that we have 100s of them. We would appreciate a PR though fixing this notification provider

@CommanderStorm commented on GitHub (Apr 17, 2025): we maintainers don't have time to track down bugs in notification providers given that we have 100s of them. We would appreciate a PR though fixing this notification provider
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3965
No description provided.