My US West 1 App is stuck with Netherlands IP?
I have an app deployed on the Hobby plan and notice HUGE latency issues here in central Canada. When I check, it gets an IP from the Netherlands when I shouldn't have anything hosted there???
I tried deleting the project and deploying the repo again, with the same results. Am I doing something wrong here? This is the only one of my projects doing this.
Solution:Jump to solution
you use njalla, they are based in finland, they dont support root level cnames, they set your domain to the ip it resolved to in finland, that would be the edge proxy in the netherlands, you need to use nameservers that do support root level cnames properly like cloudflare
23 Replies
Project ID:
e83f98ee-a559-424e-ab2e-ce343f725ceee83f98ee-a559-424e-ab2e-ce343f725cee
Should be closer to 30-50ms for what im doing
it's strange that you are hitting the Netherlands edge proxy, are you perhaps on a VPN?
I am not on a VPN, no
Same issue still. So one project resolves to US while the other resolves to Netherlands while I am querying from the same machine, back to back, without a VPN, while in Canada.
Remade the project: 1323c37e-445d-4f99-81a8-086cbc0c7302
do you have the edge proxy enabled?
I do yeah
can you send the domain?
For both
atri.dad
Just the root domain
The one that works fine is pollo.atri.dad
for whatever service is being routed via the netherlands
Ahhh
This one then
im in ontario canada and im getting that ip in the Netherlands too
Huh
It’s weird too because
Redeploying other projects of mine work fine
This one is stubborn
And I’m not sure if it’s the project, domain, or something else
what region is the actual service in though
US west
how have you verified that
I just assumed off this
That it should deploy there
Whether or not that’s actually the case, I don’t know anymore lol
even so, your request routes through edge proxies, so the ip you resolve from the domain is not the ip of the service itself
its strange that its hitting the netherlands proxy though
Yeah absolutely. I guess I’m curious if it’s a deploy issue or a routing issue
More likely the latter
Solution
you use njalla, they are based in finland, they dont support root level cnames, they set your domain to the ip it resolved to in finland, that would be the edge proxy in the netherlands, you need to use nameservers that do support root level cnames properly like cloudflare
Ohhhhh
That’ll do it…
indeed it will