File exceeds 512 MiB remote upload limit
The product is telling you this transfer is too large for the app-buffered remote path (~512 MiB). The full message suggests CDN or local staging instead.
Why this happens
When a file would be pulled or pushed through the main app toward a remote storage node, very large bodies are a bad fit for that pipe. The intended workaround is CDN / direct upload on the node, or local staging (local storage server, SFTP ingest), not streaming hundreds of megabytes through the app process.
Today, many live size checks use the tier Max upload size message instead. If you still see this text (or an older build), treat it as “too big for this remote path.”
Diagnose and fix
1. Prefer browser upload, SFTP, or direct upload on remote nodes / CDN for large files.
2. Check Users & limits → Max upload size (ul2_max_up_mb_*) and Mods → Upload hard cap (upload_hard_cap_gb) — raise only if the business allows it.
3. Assign a local storage server for staging, or enable CDN / direct upload on the remote node.
4. For Remote URL: use a smaller file, or download elsewhere and upload via Files / SFTP.
5. Confirm Remote URL upload mod and tier remote-URL block settings if the member was on that tab.