Skip to content
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

Host header smee.io causing Jenkins webhook to fail #187

Closed
dhanar10 opened this issue Mar 8, 2022 · 3 comments · Fixed by #300
Closed

Host header smee.io causing Jenkins webhook to fail #187

dhanar10 opened this issue Mar 8, 2022 · 3 comments · Fixed by #300
Labels

Comments

@dhanar10
Copy link

dhanar10 commented Mar 8, 2022

This issue starts happening to me today.

Based on my limited experiment, Jenkins BitBucket PPR webhook will fail with 404 error when it sees "host: smee.io" in request header. Removing the "host: smee.io" in request header works (I use curl to simulate this).

This is weird since smee-client has no changes for so long and the BitBucket PPR webhook plugin is last updated 3 months ago.

Does smee-client always include "host: smee.io" when invoking target webhook? If yes, then maybe an option to exlude "host: smee.io" when invoking target webhook would be nice.

@amarnath552
Copy link

amarnath552 commented Mar 26, 2022

Hi All,

I am trying to use Smee client to trigged the Job in Jenkins from git webhook. I created the new job in Jenkins and commit any change in the git, I am able to triggered the Job in Jenkins. When I tried to made any change in the git 2nd time, smee getting the response from git but job not triggered in the Jenkins. If removed the 1st build in the Jenkins and commit the changes in git it's working.
smee --url https://smee.io/XXXXXxxxxxxx --target http://127.0.0.1:8080/github-webhook/
Finally if I removed all the old builds on the job,then only new build triggered.

Can any one please suggest or provide any solution on this issue.

@amarnath552 amarnath552 mentioned this issue Mar 26, 2022
@bmerry
Copy link

bmerry commented Apr 24, 2024

This is also causing problems when using an https target: one gets a certificate error like "Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: smee.io. is not in the cert's altnames: DNS:xxx" where xxx is the target hostname.

wolfy1339 added a commit that referenced this issue Jul 22, 2024
wolfy1339 added a commit that referenced this issue Aug 15, 2024
Copy link

🎉 This issue has been resolved in version 2.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants