-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebHooks Error "There was an internal error with the Plugin, Unable to reach host: sale.jdy.com" #3306
Comments
Can you please provide some logs in your web container? It is difficult to debug this without some more information. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
我不太理解,不知还需要提供什么信息? 我在 Apifox 中可以正常调用 Webhooks Url ,但在 Sentry 中无法使用, Sentry 也只提供给我一个简单的提示信息。 |
The "Unable to reach host" message points to a problem on your networking side. You should try doing You'll need to execute this: sudo docker compose exec worker bash Then do a curl command to your target URL, like so: curl -v -X POST -H 'content-type: application/json' -d '{"action":"action","installation":"installation","data":"data","actor":{"type":"user","id":"user-id","name":"user-name"}}' https://sale.jdy.com/webhooks/yunzhijia?path=https%3A%2F%2Fwww.yunzhijia.com%2Fgateway%2Frobot%2Fwebhook%2Fsend%3Fyzjtype%3D0%26yzjtoken%3D28101b1b2e7844ffa692bbae588abdb6 If that fails, then you'll need to resolve your own networking issue, since you don't give any other details regarding that. |
Self-Hosted Version
23.6.2
CPU Architecture
unknown
Docker Version
unknown
Docker Compose Version
unknown
Steps to Reproduce
WebHooks URL: https://sale.jdy.com/webhooks/yunzhijia?path=https%3A%2F%2Fwww.yunzhijia.com%2Fgateway%2Frobot%2Fwebhook%2Fsend%3Fyzjtype%3D0%26yzjtoken%3D28101b1b2e7844ffa692bbae588abdb6
Expected Result
Webhooks was successfully enabled!
Actual Result
Event ID
No response
The text was updated successfully, but these errors were encountered: