Closed FarisZR closed 2 years ago
@fariszr Have you checked your webhook in the codeberg project settings. You should be able to see the error why the webhooks are not reaching woodpecker there.
Yes its showing up as 404 in codeberg. Do you want to send you the header ?
-------- Original Message -------- On Dec. 8, 2021, 1:08 a.m., woodpecker-ci/woodpecker - reply+aipxadu6gantl5bitgcmelv7xo6gtevbnhhd77l5eu at reply.github.com wrote:
@.***(https://github.com/fariszr) Have you checked your webhook in the codeberg project settings. You should be able to see the error why the webhooks are not reaching woodpecker there.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
The url should be something like: https://ci.example.tld/hook?access_token=xxx
.
yes the URL is showing up correctly. however all Deliveries as i mentioned before are ending up in 404 response
Weird. Could you try curl -d "access_token=justempty" -H "Content-Type: application/x-www-form-urlencoded" -X POST -i https://ci.woodpecker-ci.org/hook
It should always return a 200 even if the access token is wrong and the webhook is not handled by woodpecker (security reasons).
Can you access the UI via your reverse-proxy at all? Seems as you got the system-info from https://ci.example.tld/version
yes the UI works and i can login and manage my repos, but because the webhook doesn't work, the commits don't show up. i tried it with curl, and it gave a 200 response with the access token and without it. however manually visiting the webhook link from the browser gives a 404.
manually visiting the webhook link from the browser gives a 404.
Thats because the browser issues a GET request, that always results in an 404.
@fariszr Could you test it without nginx proxy manager. We had a possibliy similar problem in #609
@fariszr Could you test it without nginx proxy manager. We had a possibliy similar problem in #609
the server it self is giving a 404.
woodpecker | {"level":"error","time":"2021-12-17T1x:24:10Z","message":"error: FarisZR/test: cannot find in refs/heads/main: ConfigFetcher: Fallback did not found config: 404 Not Found"}
woodpecker | {"level":"error","error":"Error #01: ConfigFetcher: Fallback did not found config: 404 Not Found\n","ip":"172.18.0.3","latency":75.461209,"method":"POST","path":"/hook","status":404,"time":"2021-12-17T1x:24:10Z","user-agent":"Go-http-client/1.1","time":"2021-12-17T1x:24:10Z"}
it doesn't look like a proxy problem, since oauth and manual curl post requests are working fine.
i can confirm that woodpecker gave a 200 response with gitlab. with the exact same setup, just wiped out the data base and changed the environment to use gitlab instead of gitea.
@fariszr can you set the current location of the pipeline config in woodpercker repo settings?
@fariszr can you set the current location of the pipeline config in woodpercker repo settings?
this worked!, but is it going to work with a multi-pipeline setup ?
for the late answer ... yes this should make no difference
Component
server, web-ui
Describe the bug
Hi, I have been trying to use woodpecker with codeberg
But webhooks don't work, they are resulting in 404s woodpecker is behind Nginx proxy manager if that matters.
System Info
Additional context
Validations