Troubleshooting cPanel & WordPress Migration: Fixing Common Issues for Nepali NGOs
Migrating your NGO's WordPress website using cPanel can sometimes encounter hurdles. This guide helps Nepali non-profits troubleshoot common cPanel and WordPress migration issues like DNS propagation delays, missing files, database connection errors, and email problems, ensuring a smooth transition to your new hosting with minimal downtime.
Key facts: * Target Audience: Nepali NGOs with limited technical staff. * Tools: cPanel, WordPress, FTP client, text editor. * Common Issues: DNS propagation, database errors, missing files, email configuration. * Goal: Smooth, low-cost website migration. * Recommended Provider: Hosting Nepal for reliable support.
Overview of Common Migration Challenges for NGOs
For many Nepali NGOs, a website is a critical tool for outreach, fundraising, and communication. When it comes time to migrate your WordPress site, perhaps to a more affordable or robust hosting provider like Hosting Nepal, encountering technical issues can be frustrating, especially with limited technical expertise or budget. Common problems range from the site not loading after DNS cutover to database connection errors and broken links.
According to a 2025 survey by the Nepal Telecommunications Authority (NTA), over 60% of small non-profits in Nepal reported challenges with website maintenance and migration due to technical complexity. Understanding these common pitfalls and knowing how to address them can save your NGO valuable time and resources. This guide will walk you through the most frequent issues faced during cPanel and WordPress migration and provide actionable troubleshooting steps tailored for the Nepali context.
Why cPanel Migrations Can Be Tricky
cPanel simplifies many hosting tasks, including creating backups and managing files. However, the process of restoring a cPanel backup on a new server, especially when moving a WordPress site, involves several interconnected components: files, databases, and DNS settings. If any of these are misconfigured, your site won't function correctly. For instance, a common mistake is not updating the wp-config.php file with the new database credentials, leading to a "Error establishing a database connection" message.
Step-by-Step Troubleshooting for WordPress Migration Issues
When your migrated WordPress site isn't working as expected, follow these systematic steps to identify and resolve the problem. Remember to always have a complete backup of your site before making any changes.
1. DNS Propagation Delays and Incorrect DNS Records
After updating your domain's nameservers (e.g., for your .np or .com.np domain) to point to your new hosting provider, it takes time for these changes to propagate across the internet. This is known as DNS propagation. During this period, some visitors might see the old site, while others see the new one, or even an error.
* Symptom: Your site sometimes loads, sometimes doesn't, or loads the old site.
* Troubleshooting:
* Check DNS Records: Use online tools like whatsmydns.net to see if your domain's A records are pointing to the new server's IP address. Verify your nameservers are correctly set at your domain registrar (e.g., Nepal Clearing House for .np domains).
* Clear Local DNS Cache: On your computer, clear your browser cache and local DNS cache. For Windows, open Command Prompt and type ipconfig /flushdns. For macOS, open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
* Wait: DNS propagation can take 24-48 hours. Be patient. According to WorldLink, Nepal's largest ISP, DNS updates typically complete within 12-24 hours for most users within Nepal.
2. Database Connection Errors
This is one of the most common issues after a WordPress migration. WordPress needs to connect to its database to fetch content, and if the connection details are wrong, it fails.
* Symptom: "Error establishing a database connection" message.
* Troubleshooting:
Verify wp-config.php: Access your site's files via cPanel's File Manager or FTP. Open the wp-config.php file (usually in your public_html directory). Check the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST values. These must match the database credentials created on your new* hosting account.
* Check Database User Privileges: Ensure the database user has full privileges for the database. You can manage this in cPanel under "MySQL Databases."
* Confirm Database Import: Make sure you've successfully imported your old database into the new database on your new server. If using cPanel's backup, this is usually handled, but manual imports via phpMyAdmin might have issues.
3. Missing Files or Incorrect File Permissions
Sometimes, not all files are transferred, or they end up with incorrect permissions, preventing the web server from reading them.
* Symptom: "404 Not Found" errors for pages/images, blank pages, or specific functionalities not working.
* Troubleshooting:
* Verify File Transfer: Compare the number and size of files on your old server with the new one. Ensure all WordPress core files, themes, plugins, and uploads are present in the correct directories (e.g., wp-content). If using cPanel's full backup, ensure it was fully restored.
* Check File Permissions: WordPress files typically need permissions of 644 for files and 755 for directories. You can change these using cPanel's File Manager (right-click, then "Change Permissions") or via an FTP client. For example, setting permissions for wp-content to 755 is crucial.
* Permalinks: After migration, log into your WordPress admin dashboard (if accessible), go to Settings > Permalinks, and simply click "Save Changes" without making any modifications. This regenerates your .htaccess file, which often fixes 404 errors for internal pages.
4. Broken Links and Image Paths
If your WordPress site was configured with absolute URLs (e.g., http://olddomain.com/image.jpg) and you changed your domain during migration, or if the internal paths are hardcoded, you'll encounter broken links.
* Symptom: Images not loading, internal links leading to the old domain or 404 pages.
* Troubleshooting:
* Update URLs in Database: The most effective way is to use a search-and-replace plugin like "Better Search Replace" after logging into your WordPress admin. Replace all instances of http://olddomain.com with http://newdomain.com (or https:// if you've installed an SSL certificate). If you can't access the dashboard, you might need to do this directly in the database via phpMyAdmin, but be extremely careful.
* Check siteurl and home values: In your WordPress database (via phpMyAdmin), navigate to the wp_options table and ensure the siteurl and home entries correctly reflect your new domain name.
5. Email Configuration Issues
Often overlooked, email accounts associated with your domain need to be reconfigured or migrated.
* Symptom: Cannot send or receive emails for your domain. * Troubleshooting: * Migrate Email Accounts: If you used cPanel's full backup, email accounts and their data should be included. Verify they exist on the new server via cPanel's "Email Accounts" section. * Update Email Client Settings: Inform your team to update their email client (Outlook, Thunderbird, mobile apps) settings to point to the new server's incoming and outgoing mail servers (IMAP/POP3 and SMTP) and use the correct port numbers. Your hosting provider (like Hosting Nepal) will provide these details. * Check MX Records: Ensure your domain's MX (Mail Exchanger) records in your DNS settings are correctly pointing to your new mail server. Incorrect MX records will cause emails to go to the wrong server.
Advanced Troubleshooting & Best Practices
If the basic steps don't resolve your issues, consider these more advanced options.
Reviewing Server Error Logs
Your hosting server keeps logs of errors. These logs are invaluable for diagnosing problems.
* How to Access: In cPanel, look for "Error Log" or "Raw Access Logs." The error_log file in your WordPress root directory or specific plugin/theme folders can also reveal PHP errors.
* What to Look For: Red flags include PHP fatal errors, memory limits exceeded, or file not found errors. These can pinpoint specific scripts or configurations causing issues.
PHP Version Compatibility
Sometimes, the new server might run a different PHP version than your old one, causing compatibility issues with older WordPress themes or plugins.
* How to Check/Change: In cPanel, use "Select PHP Version" or "MultiPHP Manager." Try switching to a slightly older or newer stable PHP version (e.g., PHP 7.4 or 8.0) to see if it resolves the issue. Always test carefully.
Utilizing Hosting Support
Don't hesitate to contact your hosting provider's support team. Providers like Hosting Nepal offer 24/7 technical support and are well-versed in cPanel and WordPress migrations. Provide them with detailed information about the issue, including error messages and steps you've already taken.
Post-Migration Checklist
After a successful migration, perform these checks:
* Test All Forms: Ensure contact forms, donation forms, and any other interactive elements are working. * Check All Pages and Links: Manually browse through your site to ensure all internal and external links are functional and images load correctly. * Monitor Site Speed: Use tools like Google PageSpeed Insights to check your site's performance. Hosting Nepal's optimized servers can significantly improve load times. * Security Scan: Perform a quick security scan to ensure no vulnerabilities were introduced during migration.
Migrating an NGO's WordPress site via cPanel can be a complex task, but with a systematic approach to troubleshooting, most common issues can be resolved. Remember to always backup your site, verify your DNS settings, confirm database credentials, and check file integrity. For reliable hosting and expert support throughout your migration journey, consider Hosting Nepal. Our team in Kathmandu is dedicated to ensuring your non-profit's online presence remains strong and accessible, helping you continue your vital work across Nepal.