Troubleshooting & Advanced Configuration
Compliance and Security Best Practices
Last Updated: December 7, 2025Website Hardening Checklist Use Strong Passwords: Never use simple passwords. Enforce strong, unique passwords for all cPanel, application (e.g., WordPress admin), database, and email accounts. Update Software Regularly: Ensure your CMS (WordPress, Joomla, etc.) and all themes and plugins are updated to their latest versions. Outdated software is the number one cause of hacking. Disable Unused Services: Uninstall or disable any plugins, themes, or applications that you no longer use. Data Compliance Notes GDPR (General Data Protection Regulation): While CyberWAF provides the hosting environment, you are responsible for content compliance. Ensure you have a clear Privacy Policy, handle user data consent correctly, and use SSL encryption (provided free by CyberWAF). PCI DSS (Payment Card Industry Data Security Standard): If you process credit card data directly on your server, confirm that your payment gateway meets PCI requirements. Our WAF helps protect the application layer, but full compliance requires adherence to all PCI standards. Maximizing CyberWAF Security Enable Blocking Mode: Ensure your WAF is set to Blocking Mode for active threat mitigation. Daily Backups: Confirm that your Daily Backups (stored for 60 days) are running successfully, providing a quick recovery point in case of any disaster.
Using SSH Access and FTP for Advanced Users
Last Updated: December 7, 2025Secure Shell (SSH) Access SSH allows advanced users to interact with the server via command line, essential for running maintenance scripts, debugging, and managing large files. Enable SSH: SSH access is available upon request for security reasons. Submit a support ticket to have SSH enabled for your account. Required Credentials: Use your primary cPanel username and password. Connection Details: Connect using an SSH client (e.g., PuTTY, Terminal) with the following details: Host/IP: Your server’s IP address. Port: 22 (standard) or a custom port provided by support. File Transfer Protocol (FTP) Access FTP is used for uploading, downloading, and managing site files. Create FTP Accounts: In cPanel, navigate to “FTP Accounts.” Create a new, dedicated FTP user (recommended over using the main cPanel login). Connection Details: Server/Host: ftp.yourdomain.com or your server’s IP. Username: The full FTP account name (e.g., user@yourdomain.com). Port: 21 (standard). Best Practices for Advanced Access Security: Always use SFTP (Secure File Transfer Protocol) or SSH over standard FTP for encrypted data transfer. Permissions: Use the chmod command via SSH or the File Manager to ensure correct file permissions (755/644).
How to Clear Your Website and Browser Cache
Last Updated: December 7, 2025Understanding Caching Layers To maximize performance, modern websites use multiple layers of caching: Browser Cache: Your local computer stores static files (images, CSS) to speed up repeat visits. Application Cache: Caching plugins (WordPress, Joomla) store optimized HTML output. Server Cache: Server-side caching mechanisms (e.g., LiteSpeed Cache) for faster delivery. Step 1: Clearing Your Application Cache (CMS Users) WordPress Users: If you use a caching plugin (LiteSpeed, WP Rocket, etc.), log into your WordPress admin dashboard and use the plugin’s designated “Clear All Cache” or “Purge All” button. Other CMS: Consult your CMS documentation for purging system or third-party cache files. Step 2: Clearing Your Browser Cache This ensures your computer is requesting the latest version from the server. Hard Refresh (Quick Fix): Press Ctrl + F5 (Windows/Linux) or Cmd + Shift + R (Mac). Full Clear: Go to your browser’s history settings and clear “Cached Images and files.” Step 3: Server-Side Cache (If Applicable) If you suspect server-level caching is the issue, contact CyberWAF support. Our team can help purge the necessary server cache layers to resolve persistence issues.
How to Fix 500 Internal Server Errors
Last Updated: December 7, 2025What is a 500 Internal Server Error? A 500 Internal Server Error is a generic server-side error indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Unlike a 404 (Not Found), the 500 error means the problem lies within your website’s code or configuration. Common Causes and Solutions Faulty .htaccess File: The most common cause. A simple syntax mistake in the .htaccess file can cause a 500 error. Solution: Access your File Manager in cPanel or use FTP. Locate the .htaccess file in your root directory (public_html). Rename the file to htaccess.old. If your site loads, the issue was the file. Incorrect File Permissions: Server scripts (like PHP) and directories require specific permissions to execute safely. Solution: Use the File Manager in cPanel. Set folders to 755 permissions and files to 644 permissions. Never use 777 permissions. PHP Timeout or Memory Limit: If a script takes too long or consumes too much memory, the server may terminate it with a 500 error. Solution: Contact CyberWAF support to review your script execution time or check if your plan requires an upgrade to higher dedicated RAM/CPU resources. WAF Interaction Troubleshooting If the error started immediately after...