webhook icon indicating copy to clipboard operation
webhook copied to clipboard

Getting some TLS errors when receiving webhooks

Open st3fus opened this issue 1 year ago • 5 comments

So I'm noticing most of time hooks coming from BitBucket are failing, not sure for what reason, I'm not that much experienced with it. Here are the errors I'm getting when I do systemctl status webhook.service:

[webhook] 2023/05/15 00:46:23 http: TLS handshake error from 5.188.210.227:47566: unexpected EOF
May 15 00:46:29 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 00:46:29 http: TLS handshake error from 5.188.210.227:50464: unexpected EOF
May 15 00:46:35 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 00:46:35 http: TLS handshake error from 5.188.210.227:50972: unexpected EOF
May 15 00:47:55 ip-***-**-**-***webhook[3925]: [webhook] 2023/05/15 00:47:55 http: TLS handshake error from 5.188.210.227:36398: tls: first record does not look like a TLS handshake
May 15 00:48:58 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 00:48:58 http: TLS handshake error from 5.188.210.227:54878: tls: first record does not look like a TLS handshake
May 15 02:00:55 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:00:55 http: TLS handshake error from 167.248.133.37:47612: read tcp ***-**-**-***:9000->167.248.133.37:47612: read: c>
May 15 02:00:57 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:00:57 [c07ee3] 200 | 2 B | 8.682µs | 52.47.71.75:9000 | GET /
May 15 02:00:57 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:00:57 [1b8456] 200 | 2 B | 6.339µs | 52.47.71.75:9000 | GET /
May 15 02:00:58 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:00:58 http: TLS handshake error from 167.248.133.37:35066: tls: client requested unsupported application protocols ([>
May 15 02:04:43 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:04:43 [b91adb] 200 | 2 B | 33.968µs | 52.47.71.75:9000 | GET /
May 15 02:04:49 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:04:49 http: TLS handshake error from 184.105.139.67:33788: tls: client offered only unsupported versions: []
May 15 02:04:55 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:04:55 http: TLS handshake error from 184.105.139.67:17472: tls: no cipher suite supported by both client and server
May 15 02:05:00 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 02:05:00 [e0a36b] 200 | 2 B | 7.46µs | 52.47.71.75:9000 | GET /
May 15 03:05:04 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 03:05:04 http: TLS handshake error from 167.94.138.35:41290: read tcp ***-**-**-***:9000->167.94.138.35:41290: read: con>
May 15 03:05:05 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 03:05:05 [b6f0ad] 200 | 2 B | 6.787µs | 52.47.71.75:9000 | GET /
May 15 03:05:06 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 03:05:06 [773d8f] 200 | 2 B | 5.46µs | 52.47.71.75:9000 | GET /
May 15 03:05:06 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 03:05:06 http: TLS handshake error from 167.94.138.35:37206: tls: client requested unsupported application protocols ([h>
May 15 03:20:44 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 03:20:44 [a59615] 200 | 2 B | 6.473µs | 52.47.71.75:9000 | GET /
May 15 05:24:35 ip-***-**-**-*** webhook[3925]: [webhook] 2023/05/15 05:24:35 http: TLS handshake error from 104.237.145.157:40448: EOF

Is that the issue again with Athlassian having new IPs? Saw a PR about that...

st3fus avatar May 15 '23 11:05 st3fus

Any news?

st3fus avatar Aug 10 '23 10:08 st3fus

Now I'm getting them when build is done from GitHub with DockerHub, TLS handshake error

st3fus avatar Aug 22 '23 16:08 st3fus

Anyone having these issues?

st3fus avatar Oct 16 '23 12:10 st3fus

Still nothing? Having these issues on multiple deployments, all happening random, it's not connected strictly to BitBucket anymore, same happens when receiving a webhook from DockerHub or GitHub

st3fus avatar Dec 19 '23 12:12 st3fus

Hmm. I'm not seeing issues with Bitbucket. What do the logs say after "tls: client requested unsupported application protocols ([..."?

Can you try rebuilding webhook with the latest Go release? Looks like you're having TLS handshake issues. I'm assuming there's something wrong locally in your environment.

moorereason avatar Dec 19 '23 19:12 moorereason