To publish a website, your files must be uploaded to the server.
On Web Hosting and Site Hosting packages, this can be done using File Manager or FTP (FTPS).
Both methods achieve the same result but are suited for different situations.
Where Website Files Belong #
Website files must be uploaded to the document root of your domain.
Common document roots:
public_htmlfor the main domain- A subfolder inside
public_htmlfor addon domains or subdomains
Files uploaded outside the document root will not be publicly accessible.
Using File Manager #
File Manager is a browser-based tool inside cPanel.
What File Manager Is Good For #
File Manager is best for:
- Small websites
- Uploading a few files
- Quick edits
- Emergency fixes
- Users without FTP software
No additional software is required.
How File Manager Works #
With File Manager, you can:
- Upload files via browser
- Extract ZIP archives
- Edit files directly
- Manage folders and permissions
Uploads are limited by browser and PHP upload limits.
Limitations of File Manager #
File Manager is not ideal for:
- Large websites
- Uploading many files
- Long upload sessions
- Automated deployments
Browser timeouts may occur.
Using FTP (FTPS) #
FTP allows you to upload files using an FTP client application.
At ProRedLine, FTPS is required for secure file transfers.
FTPS Connection Details #
Important:
- Protocol: FTPS (Explicit)
- Hostname:
server.proredline.com - Authentication: Required
- Encryption: Enabled
Although cPanel may show ftp.yourdomain.com, you must use server.proredline.com.
What FTP Is Good For #
FTP is recommended for:
- Large websites
- Uploading many files
- Repeated uploads
- Development workflows
- Reliable transfers
FTP is faster and more stable for large uploads.
File Manager vs FTP Comparison #
File Manager:
- Browser-based
- No software needed
- Best for small tasks
FTP:
- Requires an FTP client
- Uses encrypted FTPS
- Best for large or frequent uploads
Both methods upload to the same server location.
Common Mistakes #
- Uploading files to the wrong directory
- Using FTP without encryption
- Using the domain name instead of
server.proredline.com - Uploading ZIP files without extracting them
These mistakes often cause websites not to load.
Testing After Upload #
After uploading:
- Visit your domain in a browser
- Check for missing files or errors
- Verify index files exist
If the site does not load, check the document root first.
Responsibility Notice #
You are responsible for:
- Uploading files to the correct directory
- Using secure FTPS connections
- Verifying website functionality after upload
ProRedLine does not upload website files on behalf of customers.
Still need help after reading this article?
