starred/uptime-kuma

Fork 0

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

Notification type "OPSGenie" - Unable to send notifications via a proxy #2736

New issue

Closed

opened 2026-02-28 03:05:17 -05:00 by deekerman · 2 comments

deekerman commented

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

Owner

Originally created by @JulienAubert9 on GitHub (Oct 31, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Hello,

With the notification integration type "OPSGenie", it's impossible to transmite notification through a proxy because the integration is not able to talk correctly to http proxy.

We see direct requests "POST https://api.eu.opsgenie.com/v2/alerts" in the logs, this is not supported.
The integration has to first open a tunnel using CONNECT method: e.g.: "CONNECT api.eu.opsgenie.com:443 HTTP/1.0"

A "curl" command is automatically do this, for example.
Please, could you add this possibility ? We use Kuma behind a proxy

Thank you in advance

👟 Reproduction steps

Configure the notification integration "OPSGenie" and use is through a proxy

👀 Expected behavior

The notification integration "OPSGenie" should be able to send notification through a proxy.

😓 Actual Behavior

Error 503 when we test to send a notification because the proxy refuse the connection

🐻 Uptime-Kuma Version

1.23.3

💻 Operating System and Arch

Portainer integration

🌐 Browser

Not relevant

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @JulienAubert9 on GitHub (Oct 31, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description Hello, With the notification integration type "OPSGenie", it's impossible to transmite notification through a proxy because the integration is not able to talk correctly to http proxy. We see direct requests "POST https://api.eu.opsgenie.com/v2/alerts" in the logs, this is not supported. The integration has to first open a tunnel using CONNECT method: e.g.: "CONNECT api.eu.opsgenie.com:443 HTTP/1.0" A "curl" command is automatically do this, for example. Please, could you add this possibility ? We use Kuma behind a proxy Thank you in advance ### 👟 Reproduction steps Configure the notification integration "OPSGenie" and use is through a proxy ### 👀 Expected behavior The notification integration "OPSGenie" should be able to send notification through a proxy. ### 😓 Actual Behavior Error 503 when we test to send a notification because the proxy refuse the connection ### 🐻 Uptime-Kuma Version 1.23.3 ### 💻 Operating System and Arch Portainer integration ### 🌐 Browser Not relevant ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

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

closed this issue
added the
feature-request

A:notifications
labels

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Oct 31, 2023):

Not a bug, but a feature request.
None of the notification providers use the proxy settings

If you'd like to contribute such a feature see our contribution guide

@CommanderStorm commented on GitHub (Oct 31, 2023): Not a bug, but a feature request. None of the notification providers use the proxy settings If you'd like to contribute such a feature see our [contribution guide](https://github.com/louislam/uptime-kuma/blob/df832f15fe21c5afc2d3e1d040bced79790962f2/CONTRIBUTING.md)

deekerman commented

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

Author

Owner

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

Duplicate of #616

@CommanderStorm commented on GitHub (Dec 10, 2023): Duplicate of #616