Remote file exceeds maximum upload size
Remote URL import refused the file because its size (from Content-Length or counted bytes) is over the member’s effective upload ceiling. The UI may show the cap in place of {maxSize}.
Why this happens
resolveEffectiveMaxUploadBytesForMember combines tier Max upload size (ul2_max_up_mb_*), site fallback, and Upload hard cap. Checked before and during from-url import. Same family as browser File exceeds maximum upload size, but for remote import.
Diagnose and fix
1. Admin → Settings → Users & limits → Max upload size for that tier — raise MB if allowed (0 = unlimited up to the hard cap).
2. Mods → Upload hard cap if the tier looks high enough but still fails.
3. Per-user override when only one account needs a higher cap.
4. Member: smaller remote file, upgrade when offered, or use browser/SFTP upload instead.
5. Unreliable origins that lie about Content-Length can also trip size checks — try another URL.