Connection requirements
Use an SFTP-capable client such as FileZilla, Cyberduck or an editor with SFTP support. Connect to the supplied file-server hostname on port 22 with the file username and password. Use the hostname rather than saving its current IP address because the service can move during infrastructure maintenance.
Verify the server identity
On the first connection, compare the SHA-256 host-key fingerprint shown by the client with the supplied fingerprint. Stop if an already trusted hostname suddenly presents a different key and no announced infrastructure change explains it. Accepting an unverified replacement key can expose the password and uploaded files to another server.
Find the correct document root
Every attached hostname maps to one relative folder. Confirm that mapping before uploading the public index file inside it. Files placed in the hosting home but outside the mapped root are not served for that hostname. Keep private configuration above the public root when the application supports it and do not delete a shared folder until every hostname using it has been identified.
Publish files safely
Take a copy of the current root before replacing a live site. Upload large trees to a temporary sibling folder when possible, verify file counts and permissions, then switch deliberately. Typical files should not be world-writable; avoid permission 777. Preserve hidden files such as .htaccess because they can control routing, access protection and HTTPS redirects.
Use Silurian File Manager
The browser file manager is intended for small, targeted operations: inspect a directory, upload or download a file, create a folder, rename an entry or remove a confirmed file or empty folder. It asks for the current password of the SFTP user identified on screen and never changes that password. If the password is unknown, set a new one from that user's action menu before connecting. The encrypted file-manager session expires after 15 minutes, and the upload limit is 25 MB per file. Use desktop SFTP for a complete application, a large archive or a transfer that must resume after interruption.
Passwords and additional users
The file-user password is separate from the Workspace password and is never redisplayed. Rotate it if it is lost or disclosed. When the plan supports additional users, create an individual account for each person and restrict it to the narrowest useful directory and protocol. Prefer SFTP; plain FTP on port 21 does not encrypt credentials or content.
Restore website files
A file restore replaces the storage state with the chosen snapshot. First download any newer files that may still be needed, especially uploads created by visitors. After restoration, test the homepage, an uploaded asset and the administration login. Dynamic sites may also require a database restore from the same point in time.
Troubleshoot a failed connection
Confirm protocol SFTP, port 22, the exact hostname and username, then check whether the password was recently changed. A timeout indicates network or service reachability rather than a bad password. Authentication failure indicates the login, password or account state. A host-key mismatch must be investigated before reconnecting.
