Moving a WordPress website is fairly easy, here are the steps: Backup your mysql database and re-import it in the new environment, Move all the files to the new environment, Update the wp-config.php file to reflect the new database connection information, (*)Replace all occurrences of your domain name with the new one if it has … Read more
Are you sure /wp-includes/load.php made it to the server? If you were installing manually, there’s a chance it got lost during the transfer. Happens to me occasionally using FileZilla. The error messages are basically telling you that the server can’t find the file, so make sure the file is there.
You could set up custom logs in your httpd-vhosts.conf depending on the HTTP_HOST variable – if your server is an Apache and you use subdomains for each single site. For sub directories (not tested): SetEnvIf Request_URI ^sitename1 sitename1 SetEnvIf Request_URI ^sitename2 sitename2 CustomLog sitename1.log common env=sitename1 CustomLog sitename2.log common env=sitename2
It appears that you don’t have the mod_rewrite module enabled in apache. This explains why you can access the dashboard found at wp-admin/index.php, but not the main index.php. Your .htaccess is depending on the rewrite module to do its work, which isn’t active. To enable it in your http.conf file you need to find the … Read more
Both servers are listening to the same port. You have Nginx set to listen to 80 and nothing is set for Apache unless it’s in your ports.conf. Your also proxy passing to Apache port 80 in your Nginx conf. In the Nginx conf change proxy_pass http://127.0.0.1:80; to proxy_pass http://127.0.0.1:9000; change listen XXX.XXX.XXX.XXX:80; to listen 80; … Read more
Solved by this lines: RewriteEngine On RewriteBase / RewriteRule ^wp-json/(.*) /?rest_route=/$1 [L]
Use a tool like phpMyAdmin to check your databases directly. Open the (your db prefix)_options table in the database for the problem site. Then check the row where option_name = siteurl and see if the option_value is correct. If not, correct it and you will be able to login to the wp-admin of that site. … Read more
The simplest answer is: As long as you’re on a fairly standard RedHat/CentOS/Fedora server, make sure that everything under your WordPress directory belongs to apache:apache. This will prevent the prompting for FTP credentials. The advantage to doing it this way is that, in almost ALL situations, Apache has /bin/false or /sbin/nologin set up as its … Read more
I think you are missing some rules in your WP .htaccess file. I show mine below. Notice the rules for wp-admin, add them to your file: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /subcataloged/cliens-wp/ RewriteRule ^index\.php$ – [L] # add a trailing slash to /wp-admin RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L] RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond … Read more
Authorization header is usually stripped by Apache. You can fix it with .htaccess RewriteEngine On RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule .* – [e=HTTP_AUTHORIZATION:%1]