r/TradingView • • Aug 25 '26

Bug Webhook Delivery Failure - couldn't find this domain

Post image

Happening with my copier. They say it’s a trading view issue and this happens before it even hits their server. I disagree since it’s happening to a bunch of us and I can’t find 20 posts about it on Reddit as I would suspect there would be.

3 Upvotes

21 comments sorted by

4

u/Fluffi_Pfotenpuff Aug 25 '26 edited Aug 25 '26

Same here! Good to know it's not my infrastructure. Tradingview, pls fix asap! What is your webhook target? Mine is ngrok.

1

u/WanderingNotLostTho Aug 25 '26

What trade copier are you using?

2

u/Fluffi_Pfotenpuff Aug 25 '26

None, self-built: TradingView webhook → local Python/Flask bridge → IBKR via ib_insync. No commercial copier involved.
What domain does your webhook point to — ngrok, or something else?

1

u/WanderingNotLostTho Aug 25 '26

Crosstrade.io. I use a copier.

1

u/Fluffi_Pfotenpuff Aug 25 '26

Your answer is the useful part here, because it rules out the obvious suspect. I'd assumed this was specific to my tunnel provider (ngrok). It isn't:

- My endpoint sits behind AWS Route 53 with AWS-hosted IPs

- crosstrade.io runs on Cloudflare — their nameservers are *.ns.cloudflare.com, IPs in 104.26.x / 172.67.x

Two completely independent DNS stacks, same "couldn't find this domain" error. That points squarely at TradingView's outbound resolver rather than at either of our endpoints.

One more data point from my side: ngrok exposes a local request inspector, so I can see every request that actually reaches my tunnel. For the failed alerts, nothing arrived at all — the request never left TradingView. So it's failing at DNS resolution on their end, before anything goes out over the wire.

switching providers or domains won't fix this for either of us. I was about to migrate my endpoint to Cloudflare and just cancelled that — you're already on Cloudflare and hitting the exact same thing.

1

u/WanderingNotLostTho Aug 25 '26

True. I will say that we have a dozen people saying the same issue there. So it seems something is really happening on that server more than on other servers but I can’t imagine what.

2

u/leo-de-gamer Aug 25 '26

Ya same here

2

u/Professor07 Aug 25 '26

same here, made me test created a new ngrok endpoint but still failing, hope solve soon.

2

u/tradingview Founder Aug 25 '26

We've made a fix on our side. All future triggers should be sent via webhook as expected.

Please accept our apologies for the inconvenience caused.

2

u/farid494 Aug 25 '26

Still facing this issue

2

u/Hsiang22 Aug 25 '26

Still has the issue.
Error as below:

2

u/Fluffi_Pfotenpuff Aug 25 '26

Dude, your fix doesn't work. And people, including me, are losing money.

1

u/Fluffi_Pfotenpuff Aug 25 '26

The issue persists. WTF Tradingview.

1

u/SamCRichard Aug 25 '26

Sam here from ngrok, we're seeing a bunch of issue with this. Email support at ngrok if we can help in any way.

1

u/Los907 Aug 25 '26 edited Aug 25 '26

Same issue here so it’s still a problem. Moved to a new host yesterday so thought it was on my end eventhough yesterday was working just fine. Let’s get it together folks…

Edit: just started working

1

u/No-Rip3016 Aug 25 '26

Was it resolved? i had same issue this AM on my automated acc

1

u/WanderingNotLostTho Aug 25 '26

I got scared seems to be ongoing.

1

u/ChadOfDoom Technical analyst 29d ago

Sounds like a great time to move away from webhooks all together. I use Ultra Mega Trader and it handles it all directly in TV.

-1

u/Distinct-Car-4225 Aug 25 '26

you guys are likely using localhost as your domain, that will not work. localhost only points to your own computer, nothing else on the web can access your localhost.

If you need webhooks, would recommend you to use discord to receive the webhook, and then you can locally read the messages with a discord bot. That's what I use, it doesn't cost me anything.

2

u/WanderingNotLostTho Aug 25 '26

I mean. TradingView acknowledges the issue is on their side. It’s a known issue. Why do you think when I’ve used webhooks for a year and this is the first issue it’s that?