# Troubleshooting
- First-look decision path
- Migration Stuck on "Downloading Files"
- Cannot Connect to FTP Server
- Database Import Failed
- WordPress Not Found
- Plugin Method Fails
- File Extraction Failed
- Connection Timeout
- Maximum Execution Time Exceeded
- Insufficient Disk Space
- Search-Replace Failed
- SSL Certificate Issues After Migration
- Using Logs for Troubleshooting
- Getting Support
- Related Documentation
This guide covers common migration issues and their solutions. When troubleshooting, always start by checking the Migration Details modal, particularly the Logs tab.
# First-look decision path
- Which tab is red/alerting? Steps or Logs → note the failing step and code.
- Is this automatic or manual?
- Automatic: consider retry/stop, or flip to manual if source blocks access.
- Manual: ensure files are uploaded + verified.
- Symptom bucket: connection, download speed/size, extraction/import, search-replace, SSL.
- Action: use the symptom sections below; if unresolved, export logs and escalate.
# Migration Stuck on "Downloading Files"
# Possible Causes
- Large file set (many files or large total size)
- Slow network connection to source server
- Source server throttling connections
- FTP connection timeout settings
# Solutions
- Wait longer - large sites can take hours to download
- Check source server logs for connection issues
- Try manual migration with pre-prepared ZIP file
- Consider splitting large sites into smaller chunks
# Cannot Connect to FTP Server
# Possible Causes
- Incorrect FTP credentials
- FTP server firewall blocking PanelAlpha
- Wrong FTP port specified
- FTP server down or under maintenance
# Solutions
- Verify FTP credentials with separate FTP client (FileZilla, Cyberduck)
- Check source server firewall rules - ensure PanelAlpha IP is allowed
- Try different port:
- Port 21 for FTP
- Port 22 for SFTP
- Port 990 for FTPS (implicit)
- Contact source hosting provider to verify FTP service status
- Check passive/active mode settings if using FTP
# Database Import Failed
# Possible Causes
- Corrupted database dump
- MySQL version incompatibility
- Insufficient MySQL privileges
- Database too large for destination server limits
- Character encoding issues
# Solutions
- Re-export database with different tool:
- Try phpMyAdmin instead of WP-CLI or vice versa
- Use
mysqldumpwith--single-transactionflag - Ensure UTF-8 encoding is used
- Check MySQL version compatibility:
- Source MySQL 8.0 may have issues with destination MySQL 5.7
- Consider upgrading destination MySQL version
- Verify database user privileges:
GRANT ALL PRIVILEGES ON database_name.* TO 'user'@'localhost'; FLUSH PRIVILEGES; - Increase MySQL settings on destination server:
max_allowed_packet = 256M(or higher)innodb_buffer_pool_sizefor large imports
- Split large database imports:
- Export individual tables
- Import in batches
# WordPress Not Found
# Possible Causes
- Incorrect path specified
- WordPress installed in subdirectory
- Non-standard WordPress structure
- Files not readable by FTP user
# Solutions
- Verify exact path to WordPress installation:
- Common paths:
/,/public_html,/public,/htdocs,/www - Check for subdirectories like
/wordpressor/blog
- Common paths:
- Look for wp-config.php:
- Navigate FTP to find
wp-config.phpfile - Use that directory as the WordPress path
- Navigate FTP to find
- Check for wp-content directory:
- Must be present alongside
wp-config.php
- Must be present alongside
- Verify FTP user permissions:
- Ensure FTP user has read access to all WordPress files
- Check file ownership and permissions
# Plugin Method Fails
# Possible Causes
- WordPress admin credentials incorrect
- Security plugins blocking login attempts
- Two-factor authentication enabled
- WordPress in maintenance mode
- Admin area protected by .htaccess
# Solutions
- Verify admin credentials:
- Test login manually in browser
- Ensure username/password are correct
- Check for special characters in password
- Temporarily disable security plugins:
- Wordfence
- iThemes Security
- Sucuri Security
- Disable 2FA for migration duration:
- Turn off Google Authenticator
- Disable Duo Security
- Take WordPress out of maintenance mode:
- Delete
.maintenancefile from WordPress root
- Delete
- Remove .htaccess restrictions:
- Check for IP restrictions
- Temporarily rename
.htaccessto.htaccess.bak
- Try manual plugin installation option instead
# File Extraction Failed
# Possible Causes
- Corrupted ZIP file
- Insufficient disk space on destination
- File permissions issues
- ZIP file too large
- Unsupported compression format
# Solutions
- Test ZIP file integrity:
- Extract locally to verify it's not corrupted
- Re-create ZIP if necessary
- Check disk space on destination server:
- Need at least 2x the ZIP size free
- Clean up unnecessary files
- Upgrade hosting plan if needed
- Fix file permissions:
- Ensure destination directory is writable
- Check hosting account ownership
- Split large sites:
- Create smaller ZIP files
- Import in stages
- Use standard ZIP compression:
- Avoid 7z, RAR, or other formats
- Use standard ZIP or gzip
# Connection Timeout
# Possible Causes
- Network connectivity issues
- Source server slow to respond
- Large file transfer interrupted
- Firewall blocking prolonged connections
# Solutions
- Retry the migration - may be temporary network issue
- Check network connectivity:
- Test with
pingortraceroute - Verify no packet loss
- Test with
- Try during off-peak hours:
- Less server load
- Better network performance
- Use manual migration for large sites:
- More control over transfer
- Can resume if interrupted
- Contact hosting provider:
- May need to whitelist IPs
- Adjust timeout settings
# Maximum Execution Time Exceeded
# Possible Causes
- PHP timeout during large data processing
- Database import takes too long
- File extraction timeout
- Search-replace operation on large database
# Solutions
- Increase PHP timeout on destination server:
max_execution_time = 600(or higher)max_input_time = 600
- Use manual migration for large sites:
- More stable for large datasets
- Optimize database before export:
- Clean up spam comments
- Delete post revisions
- Remove transients
- Split migration into smaller parts:
- Migrate files first
- Then database separately
# Insufficient Disk Space
# Possible Causes
- Destination server quota exceeded
- Hosting account disk limit reached
- Temporary files filling up disk
- Large WordPress installation
# Solutions
- Check disk space on destination:
- Use cPanel Disk Usage tool
- Run
df -hcommand
- Clean up destination server:
- Delete old backups
- Remove temporary files
- Clear caches
- Upgrade hosting plan:
- Increase disk quota
- Choose plan with more space
- Optimize source before migration:
- Remove unused plugins/themes
- Clean up media library
- Compress images
# Search-Replace Failed
# Possible Causes
- Serialized data corruption
- Special characters in URLs
- Database encoding issues
- Tables with different charset
# Solutions
- Check database encoding:
- Ensure UTF-8 charset
- Convert if necessary
- Verify URLs don't contain special characters:
- Avoid spaces, accents in domain
- Manual search-replace using WP-CLI:
wp search-replace 'old-url.com' 'new-url.com' --skip-columns=guid - Use specialized tools:
- Better Search Replace plugin
- WP Migrate DB Pro
# SSL Certificate Issues After Migration
# Possible Causes
- AutoSSL not enabled
- Domain DNS not pointed yet
- SSL validation timeout
- Firewall blocking Let's Encrypt
# Solutions
- Wait for DNS propagation (up to 48 hours)
- Manually order SSL certificate:
- Use PanelAlpha SSL management
- Or control panel's AutoSSL
- Check domain points to correct server:
- Verify A record
- Check nameservers
- Temporarily use HTTP:
- Update WordPress URLs to use http://
- Switch to HTTPS after SSL issued
# Using Logs for Troubleshooting
# Step-by-Step Process
- Open Migration Details modal
- Navigate to Logs tab
- Filter by ERROR level
- Identify the failed step
- Read error message carefully
- Check timestamps - when did it fail?
- Review WARNING messages before the error
- Look for patterns in repeated errors
- Copy relevant logs for support tickets
# What to Look For
- Connection errors: Network/firewall issues
- Permission denied: File/folder permissions
- Timeout messages: Need to increase limits
- MySQL errors: Database-specific problems
- Path not found: Incorrect directory paths
# Getting Support
If you've tried the solutions above and still need help:
- Gather information:
- Migration ID
- Error message from Logs tab
- Source hosting provider details
- Destination server details
- Export logs from Migration Details
- Take screenshots of error messages
- Note what you've already tried
- Contact PanelAlpha support with all details
# Related Documentation
- Migration Details - Understanding migration logs
- Managing Migrations - Retry and manage failed migrations
- Best Practices - Prevent common issues