mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
OpsGenie notification broken #3965
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3965
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @d11ahirst on GitHub (Feb 11, 2025).
📑 I have found these related issues/pull requests
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
📝 Relevant log output
@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