Cyclone Hosting practical guide: File Manager is powerful enough to repair a site or break it, so every edit should be reversible.
File Manager Gives Direct Access To The Website
cPanel File Manager is convenient because it works in a browser, but mistakes can affect the live site immediately. Before changing important files, create a backup or download a copy.
Know The Document Root
The primary domain commonly uses public_html, while addon domains may use separate folders. Confirm the correct document root before uploading or deleting anything.
Show Hidden Files
Configuration files such as .htaccess may be hidden by default. Enable the option to show hidden files when troubleshooting redirects, PHP settings, or access rules.
Edit Small Files Carefully
The built-in editor is useful for quick changes. For larger work, download the file, edit it locally, and upload it back. Keep the original until the change is tested.
Use Compression For Transfers
Uploading one ZIP archive can be faster than uploading hundreds of small files. Extract it into the correct directory and remove the archive afterward if it contains sensitive information.
Check Permissions Before Changing Them
Permissions control who can read, write, or execute files. Do not set everything to 777. Typical web files often use 644 and directories often use 755, but application requirements can vary.
Be Careful With Delete
Some cPanel configurations use a trash folder, while others can permanently delete files. Verify the path before confirming.
Document Important Changes
When editing .htaccess, configuration files, or application code, write down what changed. That makes rollback much easier if the site behaves differently later.
Cyclone Hosting Practical Checklist
- Create a compressed copy before changing important files.
- Show hidden files when working with configuration or .htaccess.
- Use correct permissions instead of making everything writable.
- Rename a file for testing before permanently deleting it.
When To Contact Support
Contact Cyclone Hosting support when the issue involves the hosting account, server access, DNS hosted with us, email-server settings, SSL issuance, or an error you cannot isolate. Include the domain, the exact error, the page or mailbox affected, when it began, and the troubleshooting already attempted. Never send a password in a normal support message.
What To Record For Future Reference
Keep a short change log containing the date, the setting changed, the reason for the change, and the backup or rollback point. This makes future troubleshooting faster and helps separate a hosting problem from an application change.