starred/uptime-kuma

Fork 0

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

Proxy setup for Google Chat notifications #1233

New issue

Closed

opened 2026-02-28 02:14:21 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 02:14:21 -05:00

Owner

Originally created by @beavis6511 on GitHub (Jul 5, 2022).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Hello,
I would like to use the Google Chat notifications system but I have a Timeout error:

Error: Error: Error: connect ETIMEDOUT 172.217.18.202:443
    at GoogleChat.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
    at GoogleChat.send (/app/server/notification-providers/google-chat.js:41:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Socket.<anonymous> (/app/server/server.js:1124:27)

✔️ Solution

To join the Google Chat server, I need to go through a web proxy.
It's possible to create and use proxy for monitors but not for notifications.
Solution: for notifications who use http(s) protocol, add a dropdown list to chose an existing proxy.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @beavis6511 on GitHub (Jul 5, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Hello, I would like to use the Google Chat notifications system but I have a Timeout error: ``` Error: Error: Error: connect ETIMEDOUT 172.217.18.202:443 at GoogleChat.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15) at GoogleChat.send (/app/server/notification-providers/google-chat.js:41:18) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async Socket.<anonymous> (/app/server/server.js:1124:27) ``` ### ✔️ Solution To join the Google Chat server, I need to go through a web proxy. It's possible to create and use proxy for monitors but not for notifications. Solution: for notifications who use http(s) protocol, add a dropdown list to chose an existing proxy. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:14:21 -05:00

closed this issue
added the
feature-request

A:notifications
labels

deekerman commented

2026-02-28 02:14:29 -05:00

Author

Owner

@dineshbabu179 commented on GitHub (Sep 29, 2022):

I have a similar issue with sending webhook requests to Microsoft Teams. my uptime-Kuma setup in the internal environment, any HTTP request to the internet should go through the proxy. The proxy setup for monitoring works perfectly, but the notification setup is not using the proxy setup.

Here is my log.

Error: Error: Error: connect ETIMEDOUT 52.96.36.130:443
at Teams.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
at Teams.send (/app/server/notification-providers/teams.js:149:18)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)

@dineshbabu179 commented on GitHub (Sep 29, 2022): I have a similar issue with sending webhook requests to Microsoft Teams. my uptime-Kuma setup in the internal environment, any HTTP request to the internet should go through the proxy. The proxy setup for monitoring works perfectly, but the notification setup is not using the proxy setup. Here is my log. > Error: Error: Error: connect ETIMEDOUT 52.96.36.130:443 at Teams.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15) at Teams.send (/app/server/notification-providers/teams.js:149:18) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5)

deekerman commented

2026-02-28 02:14:29 -05:00

Author

Owner

@dineshbabu179 commented on GitHub (Sep 30, 2022):

@beavis6511 I have found the solution.

in your compose file set the environment variable something like this

environment:
  HTTP_PROXY: 'http://proxy.example.com:3128'
  HTTPS_PROXY: 'http://proxy.example.com:3128'

After setting up this the proxy through env variable, my Teams notification started working.

@dineshbabu179 commented on GitHub (Sep 30, 2022): @beavis6511 I have found the solution. in your compose file set the environment variable something like this environment: HTTP_PROXY: 'http://proxy.example.com:3128' HTTPS_PROXY: 'http://proxy.example.com:3128' After setting up this the proxy through env variable, my Teams notification started working.

deekerman commented

2026-02-28 02:14:29 -05:00

Author

Owner

@canis54 commented on GitHub (Jan 11, 2023):

@dineshbabu179 Even after the environment variables HTTP_PROXY and HTTPS_PROXY have been stored in the package.json continues to run the teams notification in the error 'ETIMEDOUT'. The proxy variables set in Linux are also not used. What other option do I have to send a notification via a proxy?

@canis54 commented on GitHub (Jan 11, 2023): @dineshbabu179 Even after the environment variables HTTP_PROXY and HTTPS_PROXY have been stored in the package.json continues to run the teams notification in the error 'ETIMEDOUT'. The proxy variables set in Linux are also not used. What other option do I have to send a notification via a proxy?

deekerman commented

2026-02-28 02:14:29 -05:00

Author

Owner

@canis54 commented on GitHub (Jan 11, 2023):

my log:
Error: Error: Error: connect ETIMEDOUT 52.98.171.226:443
at Teams.throwGeneralAxiosError (/opt/uptime-kuma/server/notification-providers/notification-provider.js:38:15)
at Teams.send (/opt/uptime-kuma/server/notification-providers/teams.js:153:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Socket. (/opt/uptime-kuma/server/server.js:1189:27)

@canis54 commented on GitHub (Jan 11, 2023): my log: Error: Error: Error: connect ETIMEDOUT 52.98.171.226:443 at Teams.throwGeneralAxiosError (/opt/uptime-kuma/server/notification-providers/notification-provider.js:38:15) at Teams.send (/opt/uptime-kuma/server/notification-providers/teams.js:153:18) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Socket.<anonymous> (/opt/uptime-kuma/server/server.js:1189:27)

deekerman commented

2026-02-28 02:14:29 -05:00

Author

Owner

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

Duplicate of #616

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

deekerman referenced this issue

2026-02-28 02:36:32 -05:00

Webhook notification: Add a checkbox to send alert only when monitored service is down #1899

deekerman referenced this issue

2026-02-28 02:56:15 -05:00