Migration notice: FTP endpoint change for Scribe (now MediLogix) file transfers
Intro: We’ve rebranded from Scribe to MediLogix. As part of this name change, the FTP server name you use to send files is being updated. Only the server address is changing; your username, password, folders, and process remain the same. Please update your FTP host from inbound.scribe.com to inbound.medilogix.net.
What’s changing
- Only the FTP server address (hostname).
- Old: inbound.scribe.com
- New: inbound.medilogix.net
- Your username, password, protocol (FTP/FTPS/SFTP), port, folders, and file naming stay the same.
Who needs to act
- Anyone who uploads files to Scribe/MediLogix via FTP (manual or automated).
Quick action (most users)
- Open your FTP client or automation job settings.
- Find the “Host” or “Server” field.
- Replace inbound.scribe.com with inbound.medilogix.net.
- Keep everything else exactly as it is (username, password, port, encryption mode, passive/active mode).
- Save and connect.
- Upload one small test file to confirm success.
Step-by-step: common FTP clients
- FileZilla
- File > Site Manager > select your saved site.
- Host: change to inbound.medilogix.net.
- Verify Protocol and Encryption match what you used before.
- User/Password: unchanged.
- Connect and test upload.
- WinSCP
- Login window > select your site > Edit.
- Host name: inbound.medilogix.net.
- File protocol and Port number: unchanged.
- User/Password: unchanged.
- Save > Login and test upload.
- Cyberduck / Transmit / Other GUI
- Edit your saved connection/bookmark.
- Change Server/Host to inbound.medilogix.net.
- Leave all other settings as-is.
- Save and test.
Command-line examples (keep your existing options; only the host changes)
- Standard FTP: ftp inbound.medilogix.net
- FTPS (explicit) with lftp: lftp -e “set ftp:ssl-force true; set ssl:verify-certificate true” -u USER,PASS inbound.medilogix.net
- SFTP: sftp [email protected]
Updating scripts and automations
- Windows .bat/.cmd: change any occurrence of inbound.scribe.com to inbound.medilogix.net.
- PowerShell: $server = “inbound.medilogix.net”
- Linux shell/cron: update host in curl, lftp, sftp, or MFT tool commands.
- Managed file transfer (MFT) tools (e.g., MOVEit, Globalscape, GoAnywhere): edit the connection endpoint/host for the job or resource; do not change credentials or ports.
Test checklist (takes 2–3 minutes)
- Connect to inbound.medilogix.net with your current settings.
- Upload a small test file to your usual folder.
- Verify the file appears as expected or that your downstream process picks it up.
Troubleshooting tips
- DNS/Firewall: If your network restricts outbound traffic by host or IP, allow outbound FTP/FTPS/SFTP to inbound.medilogix.net. Your network team can resolve its IP with nslookup inbound.medilogix.net.
- Certificates/host keys: If your client validates FTPS certificates or SFTP host keys, it may prompt you to trust the new hostname. Review and accept per your company policy.
- Passive mode: Use the same passive/active setting you used before. If transfers stall, try enabling passive mode.
- Ports: Keep your existing port (commonly 21 for FTP/FTPS, 22 for SFTP).
- Permissions/paths: Your folders and permissions are unchanged. If you see “permission denied” or missing directories, contact support.
- Logs help: Share client logs/screenshots with support if you need assistance.
FAQ
- Do my username and password change? No.
- Do I need to change protocol, port, or encryption? No—use exactly what you use today; only the server name changes.
- When should I switch? Please update as soon as possible to avoid any disruption.
- The current connection address will be obsolete as of October 1st, 2025
Need help?
- If you have issues or run mission-critical automations, contact MediLogix (formerly Scribe) Support or your account team at [email protected] . Include your company name, protocol (FTP/FTPS/SFTP), client/tool, error message, and a timestamp of the failed attempt.
