Self-hosted file hosting
Sign up

Errors

Import finished but no file id returned

Remote URL import looked successful but the client never received a fileId to open.

Import finished but no file id returned

Remote URL import ended without a usable fileId, so My Files never got a new file to open — similar idea to Copy finished but no file id returned, but for URL import.

Why this happens

The client expects either:

  • NDJSON ending with { "type": "done", "fileId": "…" }, or
  • a JSON ok: true payload that includes fileId

If the stream stops after progress lines, the proxy times out, or finalize fails after headers were already sent, you get this message even though the HTTP status looked fine.

Diagnose and fix

1. Check app logs for from-url / remote import / promote-to-active failures around the same time.

2. Storage — node online, disk free, not blocked by type/MIME rules at finalize.

3. Proxy: long timeout, no buffering of the NDJSON stream (imports can run many minutes).

4. Mods / limits: Remote URL on; remote URL not blocked for the tier; uploads enabled.

5. Member: retry a smaller direct link; if it keeps failing, try browser upload or SFTP for that file.

Related