blank page after migration to new server

hamid

New member
Joined
Feb 19, 2015
Messages
3
hello
i have to a migration to new server from Old DA server to new
we have one domain with many subdomains . i have build same php and webserver on new server but now main domain.com returns blank page ,subdomain are working correctly , main domain and subdomains are most WP script
and i did
tail -f /var/log/httpd/domains/domain.com.log
tail -f /var/log/httpd/error_log

but when i browse the website nothing logged!
also there is no error_log in wordpress public_html

i am really confused and do not know where to check and troubleshoot this

display_error is ON with all option .. still blank

i renamed wp plugins folder also to disable all.. not works
 
Also try again:
cd /usr/local/directadmin/custombuild
./build rewrite_confs

Dit you also have about the same mysql version?

If the logs don't present something strange (like error 500) then it could also be a php and/or database issue.
also there is no error_log in wordpress public_html
In that case, enable it via a .htaccess file if you're not using nginx.
You could do something like this in .htaccess
Code:
php_flag display_startup_errors on
php_flag display_errors on
php_flag html_errors on
php_flag  log_errors on
php_value error_log  /home/accountname/domains/domain.coml/public_html/PHPERROR.log
don't do this too long, if you found the error, disable it right away again.
 
Did you test with only a almost emty simple index.html ( in private as https or public)
Then ofcourse with renamed htaccess so no htaccess

Cache is worse after such changes to , dns cache, template cache , rewrite cache and so on.

( links and configs did you use the same setting for yes or no using private and public html or have them linked using only public on old and new box)
 
Last edited:
Hi,

Does the domain with the blank page using WordPress? also is WordFence installed on that domain?
 
You would want to check your domain error log in /var/log/httpd/domains/domain.com.error.log
You can also enable WP debugging to investigate it.
 
Back
Top