Node 17+ localhost resolution

[ganigeorgiev]

This is related to pocketbase/pocketbase#258 and pocketbase/pocketbase#272.

In short, when the PocketBase backend is started with the default localhost:8090 address, the go dns resolver will return first the IPv4 address (aka. 127.0.0.1), and then, if available, the IPv6 version (aka. [::1]).

Node17+ for some reason favors the opposite (IPv6 first, then IPv4) and therefore when you initialize the SDK client using the localhost address, eg:

const client = new PocketBase("http://localhost:8090")

it could actually resolve to the IPv6 version ([::1]) and will result in connection failure (because the PocketBase backend will be binded only to the IPv4 version).

To fix this, you could simply provide explicitly the IPv4 localhost address, aka:

const client = new PocketBase("http://127.0.0.1:8090")

---

Since there isn't much we can do from the backend side (unless we bind to both ipv4 and ipv6 or to 0.0.0.0), we'll have to improve the SDK error reporting to make it more clear what could be the reason behind the connection failure.

[ollema]

maybe it would make sense to update the documentation/API previews as well so that they use 127.0.0.1 instead of localhost?

[ganigeorgiev]

With the latest v0.4.0 release, the original fetch error is properly stored and now will be visible in the stack trace.

Additionally, all localhost occurrences are replaced with 127.0.0.1 in both the site documentation and in the Admin UI.

[kerns]

Does this not complicate auth via providers that require localhost in the callback ? (e.g. Microsoft) 🤔