#cala-br_webhooks

1 messages ยท Page 1 of 1 (latest)

kindred quiverBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1445744823943434292

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

slow hamlet
#

hi there ๐Ÿ‘‹ looking into your question now

kindred quiverBOT
shrewd swan
#

Hi!

#

I'm trying to call a webhook on this domain

#

The domain i was using before, api.saikoo.it, was originally proxied from cloudflare

#

and the webhook was getting 502

#

I've changed the destination to the new .ai, but it's still getting 502

fluid jungle
#

Hey! Taking over for my colleague. Let me catch up.

#

Are you abel to ping the domain and get resolved your IP behind ?

shrewd swan
#

The 502 I'm pretty sure that it's coming from cloudflare, althought I don't understand why

I can see no traffic reaching my endpoints, and the cloudflare logs getting the requests and returning 502 (from origin, so probably something on my reverse proxy?)

The 502s I'm getting now on api.saikoo.ai, event tho the domain is un-proxied, I suppose are because your DNS has resolved the CF ip address (the .ai domain was proxied and I unproxied it...)

shrewd swan
#

For both the subdomains

#

I've checked the firewall too, but your IPs are not blocked

fluid jungle
shrewd swan
#

I've set up a new subdomain
This is not proxied from cloudflare

https://u1-api.saikoo.ai/stripe/webhook/subscriptions/invoice.paid

The DNS is resolving directly to my server, yet I'm still getting a 502 from your end, how can it be?

No traffic from your servers is reaching my endpoint, yet if I just simply open the url on the browser I get the logs

Can you check if this webhook (the latest I've sent) is actually sending it to u1-api.saikoo.ai?
evt_1SZp2GGbPiBbgZFF7q8dyNPa

#

It resolves to 37.187.157.152, my server's ip

fluid jungle
#

So your endpoint is responding with 502 ?

shrewd swan
#

Nope, my endpoint is not getting your request

fluid jungle
#

Which means that it's not reachable

shrewd swan
#

It's not arriving to my server, altought it's not being proxied from cloudflare now, it's just a plain DNS entry

fluid jungle
#

you need to double check with your domain/DNS provider

shrewd swan
#

And here's the corresponding log on my server...

fluid jungle
#

Ok so probably this is a ssl certification issue

#

Between checking this event evt_1SZp2GGbPiBbgZFF7q8dyNPa
I'm seeing cloudflare

#

In the response headers

#

Can you try a fresh new test ?

#

What is your DNS provider ?

shrewd swan
#

Cloudflare

#

Can you check the latest event? evt_1SZp2GGbPiBbgZFF7q8dyNPa

#

I've changed the destination to this one, but at this point I'm thinking that for that event the destination has remained set to the old one..

fluid jungle
shrewd swan
#

It's so strange tho... this other destination is getting your requests correctly... and it's pointing to the same domain...

#

I already checked this one, can you generate a new event please

Can I clone the event?

#

Done evt_1SaFKEGbPiBbgZFFbNjjc8KV

#

Which is not proxied from cloudflare, so the response should not be a CF page..

shrewd swan
#

Ok, which is at least good, because it means that it's reaching my server

fluid jungle
#

Between why you have two webhook endpoint with the same url ? we_1SaF7zGbPiBbgZFF8AYuaJjE and we_1SQXrZGbPiBbgZFF4BudF3Rt

shrewd swan
#

But why am I seeing 502?

fluid jungle
#

Maybe those are old ones

fluid jungle
#

check the deliveries for the endpoint we_1SaF7zGbPiBbgZFF8AYuaJjE

fluid jungle
shrewd swan
#

Ah ok, yeah I've tried to set a new destination, that's the reason

#

But I'm not seeing it (?)

shrewd swan
#

Ok from my logs I think that this is the one you're referring to

fluid jungle
shrewd swan
#

I think that it was sent from the new destination that I've set
The webhook signature failed, which is normal as each destination has a different secret

#

Ok I'm seeing it now

fluid jungle
#

Nice

#

Delete all other endpoints and focus on this one then and try to solve the signature failure

shrewd swan
#

The old destination is still giving 502, but they are pointing to the new destination, how can it be?

fluid jungle
kindred quiverBOT
shrewd swan
#

I really don't understand what is happening...
I've restarted the service with the correct webhook secret, and now its getting 502 again

#

And the old one is now getting 401 ๐Ÿ˜ฆ

fluid jungle
#

Why you are keeping both ?

#

It's the same URL, right ?

shrewd swan
#

Yes

#

The thing is

#

I restarted my service with the correct webhook secret

#

And now the new one is getting 502, and the old one 401

#

But I'm still not seeing the 502s on my api

#

I can't remove the old destination, I will lose some events that are pending

tawny river
shrewd swan
#

Yeah, I'm pretty sure that's it

#

I believe that the process is stopping abruptly and restarting, so you get a 502 directly from my reverse proxy (not CF)

#

I get no log of your requests simply because they kill the server lol

tawny river
#

yeah I don't know what any of that means but seems unlikely. as I said, we'd need to investigate further so please write in

shrewd swan
#

Here's the error that's probably the culprit
2025-12-03T13:33:01.2879226Z Maximum destructuring depth reached.

tawny river
#

don't understand what that has to do with us sending a JSON payload to your server or how it's related? AFAIK that's a .NET related error so the likelihood is something in your endpoint is throwing that and maybe it's causing the exception?

#

FWIW, if this was indeed a network issue and we couldn't reach the endpoint for whatever reason, we wouldn't even get a 502 response. a 5xx response is indicative of an error/exception thrown by your endpoint code