MediaLab supports FTP and UDP uploads through the Pull add-on. These methods are reliable for large or automated transfers, but issues can occur due to network or profile settings.

Control Connection Closing Due to Firewall/Router

Error: “Could not write to transfer socket: EPIPE”

• FTP uses both a control connection and a data connection. Some firewalls close idle control connections during large transfers, causing failures.
• Solution: Try a different FTP client that handles idle connections better.
• Ask your IT department to adjust firewall/router rules to keep control connections open.

Upload Failures From Misconfigured Pull Profiles

• Files may not appear in the expected folder if the pull profile is not set correctly.
• Solution: Verify the target folder is correctly set in Settings → Cloud Storage → Pull profiles.
• Use the correct Folder ID when creating FTP subdirectories.

Regenerating FTP Credentials

• If authentication fails, your FTP password may be expired or incorrect.
• Solution: Go to Settings → FTP Upload, re-activate the profile, and generate new credentials.
• Confirm the correct server (default ftp.medialab.app) and port (default 21).

Chunked Uploads for Unstable Connections

• Uploads can fail if your connection is slow or unstable.
• Solution: Enable chunked uploads in your user preferences to split files into smaller parts.
• Copy files from NAS to your local machine before uploading.
• Use FTP instead of the web uploader for very large files.

Best Practices

• Use FTP/UDP for large or automated transfers, and the web uploader for small/manual uploads.
• Test uploads with small files before scaling to bigger transfers.
• Keep FTP credentials secure; they cannot be retrieved later, only regenerated.
• If frequent issues occur, consider using ML Connect watch folders for added stability.