Notification-PushDeer: unavailable #2387

Closed
opened 2026-02-28 02:52:53 -05:00 by deekerman · 4 comments
Owner

Originally created by @kiddyyang on GitHub (Jul 17, 2023).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

When I test with Configure PushDeer, the error is reported as in the following screenshot.
image
My key is correct and has been tested successfully on other platforms.

👟 Reproduction steps

Configure PushDeer and click the Test button

👀 Expected behavior

It looks like the PushDeer server is unavailable, I'm not sure what the program's default PushDeer API URL is, now the official default one should be: https://api2.pushdeer.com.
At the same time, I hope to add a custom API URL, because PushDeer supports setting up the user's own server, not using the official server, which is what I did. The official API also provides this parameter, the name of which should be API_BASE.

😓 Actual Behavior

The screenshot of the reported error is in the description.

🐻 Uptime-Kuma Version

1.22.1

💻 Operating System and Arch

Official Docker latest version

🌐 Browser

Google Chrome 114.0.5735.199

🐋 Docker Version

Docker 24.0.2

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @kiddyyang on GitHub (Jul 17, 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 When I test with Configure PushDeer, the error is reported as in the following screenshot. [image](https://github.com/louislam/uptime-kuma/assets/11471064/349767bf-4057-4336-a47f-aa18cab8c60c) My key is correct and has been tested successfully on other platforms. ### 👟 Reproduction steps Configure PushDeer and click the Test button ### 👀 Expected behavior It looks like the PushDeer server is unavailable, I'm not sure what the program's default PushDeer API URL is, now the official default one should be: https://api2.pushdeer.com. At the same time, I hope to add a custom API URL, because PushDeer supports setting up the user's own server, not using the official server, which is what I did. The official API also provides this parameter, the name of which should be API_BASE. ### 😓 Actual Behavior The screenshot of the reported error is in the description. ### 🐻 Uptime-Kuma Version 1.22.1 ### 💻 Operating System and Arch Official Docker latest version ### 🌐 Browser Google Chrome 114.0.5735.199 ### 🐋 Docker Version Docker 24.0.2 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_
deekerman 2026-02-28 02:52:53 -05:00
Author
Owner

@CommanderStorm commented on GitHub (Jul 17, 2023):

https://pushdeer.com/ seems to be down, but https://www.pushdeer.com/ seems not.
According to https://www.pushdeer.com/dev.html we are using their API correctly

See:

github.com/louislam/uptime-kuma@8e72d6f534/server/notification-providers/pushdeer.js (L11-L29)

@CommanderStorm commented on GitHub (Jul 17, 2023): https://pushdeer.com/ seems to be down, but https://www.pushdeer.com/ seems not. According to https://www.pushdeer.com/dev.html we are using their API correctly See: https://github.com/louislam/uptime-kuma/blob/8e72d6f5341a6c916408fc40bf81cf04173dffe6/server/notification-providers/pushdeer.js#L11-L29
Author
Owner

@kiddyyang commented on GitHub (Jul 18, 2023):

https://pushdeer.com/ seems to be down, but https://www.pushdeer.com/ seems not. According to https://www.pushdeer.com/dev.html we are using their API correctly

See:

github.com/louislam/uptime-kuma@8e72d6f534/server/notification-providers/pushdeer.js (L11-L29)

Thank you very much for your reply, after my testing, I realized that I was misled by the error message. Since I am in self-hosted mode and have my own push-link, could you please set the part of link "https://api2.pushdeer.com/" to a configurable parameter on the page?

https://www.pushdeer.com/selfhosted.html

@kiddyyang commented on GitHub (Jul 18, 2023): > https://pushdeer.com/ seems to be down, but https://www.pushdeer.com/ seems not. According to https://www.pushdeer.com/dev.html we are using their API correctly > > See: > > https://github.com/louislam/uptime-kuma/blob/8e72d6f5341a6c916408fc40bf81cf04173dffe6/server/notification-providers/pushdeer.js#L11-L29 Thank you very much for your reply, after my testing, I realized that I was misled by the error message. Since I am in self-hosted mode and have my own push-link, could you please set the part of link "https://api2.pushdeer.com/" to a configurable parameter on the page? https://www.pushdeer.com/selfhosted.html
Author
Owner

@CommanderStorm commented on GitHub (Jul 18, 2023):

Okay, so not a bug, right?

In this case:
Could you recreate this issue with the different fields in the feature_request template?
Rationale:

  • only louis can change tags
  • This removes the Server Error confusion

Alternative:
If you want to provide a PR for this, this would be appreciated. Such a PR should include screenshots that the notification provider works using https://api2.pushdeer.com/ before and after making this parameter configurable.

@CommanderStorm commented on GitHub (Jul 18, 2023): Okay, so not a `bug`, right? In this case: Could you recreate this issue with the different fields in the [`feature_request`](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=feature-request&projects=&template=feature_request.yaml) template? Rationale: - only louis can change tags - This removes the `Server Error` confusion Alternative: If you want to provide a PR for this, this would be appreciated. Such a PR should include screenshots that the notification provider works using `https://api2.pushdeer.com/` before and after making this parameter configurable.
Author
Owner

@kiddyyang commented on GitHub (Jul 19, 2023):

feature_request

Yes, sure, this is not a bug, I'll close this issue and re-submit a feature request, Thank you very much for your kind help.
But I'm sorry I don't have the development capacity to provide this PR.

@kiddyyang commented on GitHub (Jul 19, 2023): > [`feature_request`](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=feature-request&projects=&template=feature_request.yaml) Yes, sure, this is not a bug, I'll close this issue and re-submit a feature request, Thank you very much for your kind help. But I'm sorry I don't have the development capacity to provide this PR.
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#2387
No description provided.