Errors

Remote import failed

Generic client fallback when remote URL import reports an error without a clear message.

Remote import failed

A catch‑all on the Remote URL tab when the NDJSON stream sends an error event without a usable message string. Most real failures show a more specific line (timeout, size, S3, DNS, and so on).

Why this happens

The client expects each error line to include a human message. If the stream is truncated, proxied oddly, or the payload is malformed, you only get this generic text. Server-side import failures normally pass a concrete reason through runMemberRemoteUrlImport.

Diagnose and fix

1. Open DevTools → Network → from-url and read the NDJSON lines for a specific message.

2. Check app logs around runMemberRemoteUrlImport / storage write for the same timestamp.

3. Confirm Remote URL mod on, tier not blocked, uploads enabled, and storage node healthy.

4. Retry a small direct https:// URL. If you get a clearer message, follow that article instead (timeout, max size, S3, and so on).

Related