File Manager is convenient for small updates; SFTP is better for repeat deployments and large transfers. Prefer SFTP over unencrypted FTP whenever the service supports it.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Identify the document root: Check the domain settings for the exact directory that serves the site. The primary domain often differs from addon domains.
- Prepare a backup: Download or snapshot the current site before replacing files.
- Upload safely: Transfer the files, preserve the directory structure, and extract archives only inside the intended site directory.
- Check the entry file: Confirm that index.php or index.html exists directly in the document root and that filename capitalization matches links.
- Test and clean up: Load several pages, then remove leftover archives and deployment files that should not be public.
Important notes
- Typical file permissions are 644 for files and 755 for directories, but application requirements can vary.
- Never place database exports, .env files, or private keys in a public directory.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
