search

louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
52.46k stars 4.72k forks source link

Setting up pushplus push via webhook, but not receiving pushes #4870

Open mikelin8 opened 2 weeks ago

mikelin8 commented 2 weeks ago

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

🛡️ Security Policy

📝 Describe your problem

As shown in the picture, after I configured this, the token is also correct

QQ图片20240620183547

Clicking on test also prompts success without any errors being reported image

Why am I still not getting pushes from pushplus? What's wrong with it?

📝 Error Message(s) or Log

image There are no error logs

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

centos 7.9.2009

🌐 Browser

edge

🖥️ Deployment Environment

CommanderStorm commented 2 weeks ago

First of all, I translated your issue to english via deepl.com

The log you showed should not have caused a notification. You have set retries=2 and only one retry is written into the log excerpt.

mikelin8 commented 2 weeks ago

The log you showed should not have caused a notification. You have set retries=2 and only one retry is written into the log excerpt.

These logs are all normal logs, none of them report errors about webhook, the current claim is that I set up push, but my pushplus is not receiving the push

CommanderStorm commented 2 weeks ago

I don't think you are reading what I am writing as I mean it. There is no ping that should be done based on the logs you have submitted.

=> Please submit the part of the log where you expected the notification

crazybird commented 3 days ago

Error log:

Error: Error: Error: getaddrinfo EAI_AGAIN www.pushplus.plus
    at Webhook.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
    at Webhook.send (/app/server/notification-providers/webhook.js:57:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Socket.<anonymous> (/app/server/server.js:1298:27)
CommanderStorm commented 3 days ago

@crazybird your issue is unrelated: Your issue is that your DNS Provider does not return a response for that dns entry. You will need to query fewer times or