Issue Git webhook gives 404 error

[Johannes Kingma]

Server operating system version

Linux 3.10.0-962.3.2.lve1.5.83.el7.x86_64

Plesk version and microupdate number

Plesk Obsidian 18.0.60

The URL generated here


results in a 404 error.

Another domain for the same customer has a proper, working Webook-URL

What should we do to get this working?

 

[Kaspar@Plesk]

The Webhook URL is not a webpage. It will always return a 404 error in a browse because the webhook URL only works with POST requests. When you are trying to just load the URL in your browser, then you will get a 404 as that you are sending a GET request.

 

[Johannes Kingma]

Oh thanks, didn't know that. But currently also GitHub claims a 404 error when I add the webhook. Is there a way to test this and find out what the root cause is? Plesk or GitHub?

 

[Johannes Kingma]

A better reply would be 405 btw. would indicate a proper url but a wrong method. Is there someplace I can suggest this?

 

[Kaspar@Plesk]

Oh thanks, didn't know that. But currently also GitHub claims a 404 error when I add the webhook. Is there a way to test this and find out what the root cause is? Plesk or GitHub?

Are you sure GitHub is returning a 404 and not another error?

A better reply would be 405 btw. would indicate a proper url but a wrong method. Is there someplace I can suggest this?

Plesk UserVoice would be te perfect place to add this as a suggestion.

 

[Kaspar@Plesk]

That the most likely cause for a 404 wehen adding the webhook in Github would be because of a incomplete URL. Make sure you copy and post the whole URL (not forgetting any charters).

 

[Johannes Kingma]

That the most likely cause for a 404 wehen adding the webhook in Github would be because of a incomplete URL. Make sure you copy and post the whole URL (not forgetting any charters).

As Plesk copies the complete URL when single clicking it the possibilty of losing characters it negliable.

 

[Kaspar@Plesk]

As Plesk copies the complete URL when single clicking it the possibilty of losing characters it negliable.

That's true.

You could try to deleted the repository from the domain and add it again. That will generate a new webhook URL for the repository. However I suspect that the issue is caused by something else. Maybe blocking by firewall of fail2ban.