ENOTFOUND provision.convex.dev
lately i've been seeing this error when running
pnpm convex dev
I have to retry, sometimes multiple times, until it works again.
I am connected to the internet because I can browse. Although maybe I have some intermitent signal that is causing this issue.
I wonder why is this happening.16 Replies
Hey sorry for the delay. Is this still happening, and is it correlated with anything, like being on a different network?
And are you on the latest convex version, etc?
It stopped happening. I’ll keep an eye on it. I’m on the latest version
I'm also seeing this error, it does go away most of the time once I turn the VPN but without VPN I can't use Convex. I live in Bali Indonesia. Are you still seeing this issue @Gorka Cesium also @ian any guesses on why this happening ?
All good Since i fixed my wifi conectivity
hmm weird, so for me at least I know it's not wifi issue as I work in different co-working spaces regularly and it always the case without vpn I can't use convex
Hey @fawwaz, next time you run into this issue can you try capturing the output of
dig provision.convex.dev and traceroute convex.dev (assuming you're on on a linux or mac system)?
we certainly don't expect any region-based blocking to our systems, but this would help us investigate further.
when you do use a VPN to get around this issue, does your VPN exit elsewhere in Indonesia, or a different country/region entirely?Hey @gautamg the for me at least here in Bali the issue is all the time, take a look at the screen capture. When use VPN I think as long as I choose UK or USA things work without problems. let know if you see anything odd in the logs above
also @gautamg I noticed that actually if I just run the nextjs app and not the convex dev server the entire app works as expected. However, you can't make any changes to your convex code
Hey @gautamg 👋 just want to check if you had any luck figuring out the reason behind this one?
hey @fawwaz I haven't had a chance to dig deeper yet. Could you also include the
traceroute provision.convex.dev output? I think I didn't see it in the above screenshothey @gautamg I ran
traceroute provision.convex.dev and that one took quite a while!
Hello again @gautamg just want to follow up if you had any luck figuring out this issue?
Hey @fawwaz sorry for the delay. I don't have a conclusive answer yet -- my best guess is that for some reason your ISP is blocking the route to our IP addresses, but I don't have any idea why that would be the case. I'm going to poke around online and see if I can find any similar reports
Yeah that was also my thought but I doubt my ISP know Convex let along decide to block. My guess they are blocking something that somehow is linked to Convex
yeah, we're hosted in AWS at the moment so it'd have to be an AWS IP -- but it's still very surprising that they'd be blocking any AWS IP range