• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Issue with Plesk Git webhook - Timeout error and no deployment or pulling

Nathan2

New Pleskian
Server operating system version
Ubuntu 22.04 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.53.2
Hey,,

I'm encountering an issue with the Plesk Git webhook feature and would appreciate your assistance. Currently, I am using Plesk Obsidian 18.0.53.2 on Ubuntu 22.04 x86_64.

The webhook URL I'm utilizing is structured as follows: https://DOMAIN:8443/modules/git/public/web-hook.php?uuid=UUID.

Unfortunately, I'm experiencing a timeout error, and no action seems to occur on the Plesk side. Specifically, there is no deployment or pulling visible. Interestingly, clicking on the "pull" and/or "deploy" buttons works perfectly fine.

If anyone has encountered a similar problem or has any insights on how to resolve this issue, I would greatly appreciate your help.

Thank you in advance for your support!
 
You can specify which git hosting you are using (GitHub, BitBucket).
Try to enable debug
Code:
[debug]
enabled = 1
and initiate a hook call
 
It hapened to me on bitbucket, the roblem was this...
the webhook url showed in plesk was kinf of:

I made the test with postman and i got timeout request error, so i tried changing the url for this:

and i got a http 204 response (success but empty), and with an error on the ssl certificate, because i had another domain certificate by default, kind of myanotherdomain.com,
so in bitbucket I checked the "skip certificate verification" and it worked!

After all, I changed the default certificate on my server because i wanted to use mydomain.com on webhooks whitout skipping the certificate verification.
That's all. I hope it helps anyone! GBY
 
Back
Top