search

ncarlier / webhookd

A very simple webhook server launching shell scripts.
MIT License
894 stars 80 forks source link

webhoook error 503 when the hook address with https via haProxy #101

Closed iptvcld closed 1 month ago

iptvcld commented 1 month ago

webhoook error 503 when the hook address with https via haProxy I have haProxy set to the IP:8080 but when using the https address on Kuma, i get 503 service unavailable. The certs are stored on my pfsense. How can i get webhookd to work this way?

ncarlier commented 1 month ago

503 means that HAProxy failed to contact Webhookd. What is your HAProxy configuration? Do you see any error on Webhookd side. You can enabled http logger module to verify Webhookd access logs (WHD_LOG_MODULES=http).

Le sam. 10 août 2024, 23:01, iptvcld @.***> a écrit :

webhoook error 503 when the hook address with https via haProxy I have haProxy set to the IP:8080 but when using the https address on Kuma, i get 503 service unavailable. The certs are stored on my pfsense. How can i get webhookd to work this way?

— Reply to this email directly, view it on GitHub https://github.com/ncarlier/webhookd/issues/101, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGCKW4V32Q55I3RECDGTT3ZQZ5RXAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMRYHEYDCMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

iptvcld commented 1 month ago

503 means that HAProxy failed to contact Webhookd. What is your HAProxy configuration? Do you see any error on Webhookd side. You can enabled http logger module to verify Webhookd access logs (WHD_LOG_MODULES=http). Le sam. 10 août 2024, 23:01, iptvcld @.> a écrit : … webhoook error 503 when the hook address with https via haProxy I have haProxy set to the IP:8080 but when using the https address on Kuma, i get 503 service unavailable. The certs are stored on my pfsense. How can i get webhookd to work this way? — Reply to this email directly, view it on GitHub <#101>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGCKW4V32Q55I3RECDGTT3ZQZ5RXAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMRYHEYDCMQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

this is whats on webhookd side

webhookd -hook-scripts /home/webhookd/scripts -log-modules http         
time=2024-08-10T21:22:15.086Z level=INFO msg="server started" addr=:8080

and this is the HAproxy from pfsesne image

i dont see any errors or logs being produced, and Kuma has this https://mmkuma.example.com/mmtest

before coming to webhookd - this is working fine using GO Http Server for webhooks

ncarlier commented 1 month ago

Does a simple curl http://10.200.1.44:8080 inside your private network works?

Le sam. 10 août 2024, 23:24, iptvcld @.***> a écrit :

503 means that HAProxy failed to contact Webhookd. What is your HAProxy configuration? Do you see any error on Webhookd side. You can enabled http logger module to verify Webhookd access logs (WHD_LOG_MODULES=http). Le sam. 10 août 2024, 23:01, iptvcld @.

> a écrit : … <#m8660083425846079072> webhoook error 503 when the hook address with https via haProxy I have haProxy set to the IP:8080 but when using the https address on Kuma, i get 503 service unavailable. The certs are stored on my pfsense. How can i get webhookd to work this way? — Reply to this email directly, view it on GitHub <#101 https://github.com/ncarlier/webhookd/issues/101>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGCKW4V32Q55I3RECDGTT3ZQZ5RXAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMRYHEYDCMQ https://github.com/notifications/unsubscribe-auth/AAGCKW4V32Q55I3RECDGTT3ZQZ5RXAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMRYHEYDCMQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

this is whats on webhookd side

webhookd -hook-scripts /home/webhookd/scripts -log-modules http time=2024-08-10T21:22:15.086Z level=INFO msg="server started" addr=:8080

and this is the HAproxy from pfsesne image.png (view on web) https://github.com/user-attachments/assets/d0d0def2-78b3-4074-ae43-048b69796971

— Reply to this email directly, view it on GitHub https://github.com/ncarlier/webhookd/issues/101#issuecomment-2282280798, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGCKW5PT5HX2JXSKGHGKRDZQ2AILAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGI4DANZZHA . You are receiving this because you commented.Message ID: @.***>

iptvcld commented 1 month ago

yes http is working great. I have a cloud based uptime kuma server outside of my network that i need to send this webhook to and thats https - which is not sending anything

ncarlier commented 1 month ago

I don't think that the issue is related to webhookd. Maybe an issue with your pfense TLS configuration? Maybe you can try to replace webhookd with https://github.com/darklynx/request-baskets to check the network access?

Le sam. 10 août 2024, 23:50, iptvcld @.***> a écrit :

yes http is working great. I have a cloud based uptime kuma server outside of my network that i need to send this webhook to and thats https - which is not sending anything

— Reply to this email directly, view it on GitHub https://github.com/ncarlier/webhookd/issues/101#issuecomment-2282285489, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGCKW5YDECAQ5CUOABFM63ZQ2DKBAVCNFSM6AAAAABMKD3COCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGI4DKNBYHE . You are receiving this because you commented.Message ID: @.***>

iptvcld commented 1 month ago

I have it working using go http server - same config i have in haproxy.

It seems like webhookd is only accepting http and if i want https, it wants the cert files but the ssl offloading is already happening on pfsense haproxy.

iptvcld commented 1 month ago

ahhh.. i deleted the pfsense backend for haproxy and recreated it - works!! Sorry about that!