Wordpress Multisite No Longer Works on New EC2 Instance

jeffrey_veffer 2017-04-15 18:02:44 UTC #1

Hi there!
I did open a new thread with the following information:

I am trying to get my app running again on EC2 after migrating to a new instance as suggested by support to get updated versions of Apache and PHP.
I have tried several things to solve the issue including re-installing the database several times and checking the tables on the new instance vs the old one.
I currently can't get the site running on the new instance (that currently is only a dynamic IP - the static IP I have is still in the DNS for the old one as I am not sure if I have to start over with the new instance.)

Since I migrated a WP Multisite to a new host, here is what I checked

Both installations should be WP Multisite.

Yes

The domain should match in both cases, or WP multisite might not be able to detect which pages you're trying to access.

Not sure is I understand as the first I have the DNS pointing to wellclientapp.com. The second is the default name bitnami gives it which is wellclientapp-alt5.bitnamiapp.com

The /opt/bitnami/apps/wordpress/htdocs/wp-config.php file should be configured in a similar way, in terms of domain configuration, table prefixes, and WP Multisite-specific configuration (SUBDOMAIN_INSTALL, PATH_CURRENT_SITE, etc.).

These are the same in both wp-config.php files. The
define( 'DOMAIN_CURRENT_SITE', 'wellclientapp-alt5.bitnamiapp.com' );
is for the new instance and
define( 'DOMAIN_CURRENT_SITE', 'wellclientapp.com' );
is for the original

The main challenge is that I was trying to remove an expired Comodo Wildcard SSL certificate and replace is with the AMAZON signed SSL using Cloudfront. When I get the application up again, that is the next task, but for now I hope we can just get it up and running!
Thank you very much

jariza 2017-04-17 14:03:11 UTC #3

Hello @jeffrey_veffer

Thanks for opening this new thread so everything is much clearer.

What steps did you deploy in order to do so? Please describe step by step how you perform the migration.

Could you also describe your WP Multisite Configuration on the old server? Something like:

Blog 1
- Domain: XXXX
- Configuration: XXXX
Blog 2
- Domain: XXXX
- Configuration: XXXX
...

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-17 14:23:27 UTC #4

I created a backup of the DB using this guide: https://docs.bitnami.com/bch/components/mysql/#how-to-create-a-database-backup
I then used bitnami to create a new WP multisite instance.
I then restored the backup in the new instance, and ran these commands (they are similar to the ones on this guide https://docs.bitnami.com/bch/components/mysql/#how-to-restore-a-database-backup)

mysql -u root -p
mysql> drop database bitnami_wordpress;
mysql> create database bitnami_wordpress;
mysql> grant all privileges on bitnami_wordpress.* to 'bn_wordpress'@'localhost' identified by 'thePasswordInTheWPConfigFileOfTheNewInstance';
mysql> flush privileges;
mysql> exit;
mysql -u root -p bitnami_wordpress < backup.sql

I couldn't get the app to respond after this. Not sure if its a DNS issue so that perhaps temporarily have wellclientapp.com ---> this new instance [wellclientapp-alt5.bitnamiapp.com]?

There are several blogs
Main blog is wellclientapp.com which is where the network admin is located.

wellclientapp.com
client001.wellclientapp.com
test001.wellclientapp.com [has been deleted but the database listing still shows it]

etc.

jariza 2017-04-18 10:09:29 UTC #5

Hello @jeffrey_veffer

Basically the issue is that you create and restore the backup of your database but there are other configuration files that must be backed up too (basically Apache and WP configuration).

On your old server, you will have several Apache configuration files at /opt/bitnami/apps/wordpress/conf/* and you will also have the WP configuration file: /opt/bitnami/apps/wordpress/htdocs/wp-config.php.

You need to backup all those configuration file and substitute the equivalent files in the new server with those ones. Once you have the same configuration files, restart apache:

sudo /opt/bitnami/ctlscript.sh restart apache

Remember that you need to have the same database password at the wp-config.php file you indicated in the grant command to MySQL.
Note that you could have some references to the old server IP. Update any reference to the old server IP with the new one.

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-18 16:47:51 UTC #6

Thanks
I downloaded the old server config files as above and replaced them on the new server. I updated the password in wp-config.php as per the new server permissions.
After restarting the server and setting the DNS to the IP of the new server, I get two different behaviors.
After bypassing the security warning for the expired certificate, and I type in the IP directly the error comes up:

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies.

If I go to wellclientapp.com or client001.wellclientapp.com I get the bitnami welcome page for WP multisite, but the link is not working.

Awesome! WordPress is now installed.

Access WordPress

You just installed WordPress using Bitnami - the fastest, easiest and most secure way to deploy your favorite app.

Bitnami WP Multisite Stack
Visit the Bitnami WordPress documentation page for more information on managing your installation.
Access the built-in management tool phpMyAdmin. For security reasons it is only accessible when using 127.0.0.1 as the hostname.
Find answers to common questions or pose a new question on our community forum.
Thanks for using Bitnami!

I looked for outdated server names in the config files, but couldn't see any....
Can you assist?

Thanks!

jariza 2017-04-19 08:49:14 UTC #7

Hello @jeffrey_veffer

Let's take a look to your configuration files to see if there's something strange. Could you provide the following configuration files?

/opt/bitnami/apps/wordpress/conf/httpd-app.conf /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf /opt/bitnami/apps/wordpress/conf/httpd-prefix.conf /opt/bitnami/apps/wordpress/htdocs/wp-config.php

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-19 12:10:06 UTC #8

OK, I sent the files by email

thanks!

jariza 2017-04-20 09:48:59 UTC #9

Hello @jeffrey_veffer

I don't see anything weird on your configuration files. Please deploy the next actions:

Comment the line that adds the httpd-prefix.conf file for Wordpress at /opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf. It should look like:

# Bitnami applications installed in a prefix URL
# Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"
Include "/opt/bitnami/apps/phpmyadmin/conf/httpd-prefix.conf"

Add a line including the httpd-vhosts.conf file for Wordpress at /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf. It should look like:

# Bitnami applications installed in a Virtual Host
Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"

Recover the certificates that you had on your previous installation. Basically, backup all the files that you previously had at /opt/bitnami/apps/wordpress/conf/certs and put them in the same directory in the new intance.
Restart Apache:

sudo /opt/bitnami/ctlscript.sh restart apache

Let's see if that fix your problems.

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-20 13:14:04 UTC #10

Hi there:
The lines were already existing in these files as above and when I restarted the server, I couldn't ping the instance

--- 54.236.240.62 ping statistics ---
28 packets transmitted, 0 received, 100% packet loss, time 27215ms

Thanks!

jariza 2017-04-20 15:22:06 UTC #11

Hello @jeffrey_veffer

Did you find any issue when running the command ?

sudo /opt/bitnami/ctlscript.sh restart apache

Can you share with us the content of /opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf and /opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf? (just paste here the content).

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-20 16:49:34 UTC #12

Here is the response when I restarted Apache using

sudo /opt/bitnami/ctlscript.sh restart apache

Unmonitored apache
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd stopped
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80
Monitored apache

Here is bitnami-apps-prefix.conf

# Bitnami applications installed in a prefix URL
# Include "/opt/bitnami/apps/phppgadmin/conf/httpd-prefix.conf"
Include "/opt/bitnami/apps/phpmyadmin/conf/httpd-prefix.conf"
# Include "/opt/bitnami/apps/rockmongo/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/zendframework/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/symfony/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/codeigniter/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/cakephp/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/smarty/conf/httpd-prefix.conf"
#Include "/opt/bitnami/frameworks/laravel/conf/httpd-prefix.conf"
#Include "/opt/bitnami/apps/wordpress/conf/httpd-prefix.conf"

Here is bitnami-apps-vhosts.conf

> # Bitnami applications installed in a Virtual Host
> Include "/opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf"

Thanks!

jariza 2017-04-21 08:39:28 UTC #13

Hello @jeffrey_veffer

Everything seems fine. As you can see in the command, the Apache syntax is fine and it's able to start without any issue. You should be able to access your server.

You previously mentioned that you could not ping your instance after restarting it. Could you please confirm that the IP of your server didn't change after restarting it? You might be trying to ping an IP which does not belong to your server anymore. If you are able to connect to your sever via SSH you should be able to ping it (unless you block ICMP port).

Regarding the too many redirections issue. Do you see anything within the Apache log files that gives you any hint about the problem in the configuration?

/opt/bitnami/apache2/logs/error_log
/opt/bitnami/apache2/logs/access_log

Best Regards,

Juan Ariza

jeffrey_veffer 2017-04-21 12:44:46 UTC #14

Hi there!
I pinged both the IP and the Public DNS and neither respond. I then used an external tool and pinged the Public DNS and it didn't get a response. I can SSH to the instance fine...

Here are the common errors from error_log:

[Thu Apr 20 23:24:03.241579 2017] [core:error] [pid 2189:tid 139942952744704] [client 212.237.10.57:36029] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

[Thu Apr 20 23:42:53.985634 2017] [proxy_fcgi:error] [pid 2190:tid 139942961137408] [client 66.249.66.171:44569] AH01071: Got error 'PHP message: PHP Warning: include(/opt/bitnami/apps/wordpress/htdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /opt/bitnami/apps/wordpress/htdocs/wp-settings.php on line 84\nPHP message: PHP Warning: include(): Failed opening '/opt/bitnami/apps/wordpress/htdocs/wp-content/advanced-cache.php' for inclusion (include_path='.:/opt/bitnami/php/lib/php') in /opt/bitnami/apps/wordpress/htdocs/wp-settings.php on line 84\n'

[Thu Apr 20 13:07:47.286498 2017] [ssl:warn] [pid 2179:tid 139943717553984] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name

[Thu Apr 20 19:21:27.036774 2017] [proxy_fcgi:error] [pid 2392:tid 139943145776896] [client 54.236.240.62:53968] AH01071: Got error 'PHP message: PHP Warning: include(/opt/bitnami/apps/wordpress/htdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /opt/bitnami/apps/wordpress/htdocs/wp-settings.php on line 84\nPHP message: PHP Warning: include(): Failed opening '/opt/bitnami/apps/wordpress/htdocs/wp-content/advanced-cache.php' for inclusion (include_path='.:/opt/bitnami/php/lib/php') in /opt/bitnami/apps/wordpress/htdocs/wp-settings.php on line 84\n', referer: http://client001.wellclientapp.com/wp-cron.php?doing_wp_cron=1492716086.9747169017791748046875

For Access_log the most common entries are:

211.6.121.141 - - [19/Apr/2017:08:12:00 +0000] "GET /wp-signup.php?new=wellclientapp.com HTTP/1.1" 302 -

localhost - - [19/Apr/2017:08:14:01 +0000] "GET /server-status?auto HTTP/1.1" 200 615

66.249.66.156 - - [20/Apr/2017:19:11:07 +0000] "GET /login/?redirect_to=%2F&reauth=1 HTTP/1.1" 404 204

Thanks!!

jeffrey_veffer 2017-04-24 21:43:23 UTC #15

Hi there!
Please let me know if you have any suggestions on this issue.

Thanks!

jota 2017-04-25 09:44:32 UTC #16

Hi Jeffrey,

Sorry for the delay in getting back to you. I'm reading all your posts again in order to understand what the current status of your installation is. I'll provide you some points to check later today.

Regards,
Jota

jota 2017-04-25 16:15:35 UTC #17

Hi @jeffrey_veffer,

I've just checked that the DNS is properly configured and it's pointing to the IP of your machine.

https://www.whatsmydns.net/#A/wellclientapp.com

Regarding the steps I mentioned in this post

Could you please confirm that you modify the "thePasswordInTheWPConfigFileOfTheNewInstance" string with the password that is in the wp-config.php file of the new installation? In case you're not sure, could you please run the follow the next steps?

Get the database password in the wp-config.php file of WordPress.

Run the following commands:

mysql -u root -p
mysql> grant all privileges on bitnami_wordpress.* to 'bn_wordpress'@'localhost' identified by 'thePasswordYouGot';
mysql> flush privileges;
mysql> exit;

Is it accesible the application now? The ERR_CONNECTION_TIMED_OUT error message could be because the connection with MySQL can't be stablished.

I'll also try to reproduce the issue with 2 machines. I'll launch 2 different WordPress machines (one with an old version of WordPress and the other one with the new version) and will migrate the data from the old one to the new one.

Regards,
Jota

jeffrey_veffer 2017-04-25 17:20:30 UTC #18

Hi there!
I checked and the wp-config.php file has the correct pwd for the new instance.
Even when I went through the steps above I couldn't access the instance, but here is the response from the server. Note that it says "0 rows affected"

mysql> grant all privileges on bitnami_wordpress.* to 'bn_wordpress'@'localhost' identified by 'thePasswordInTheWPConfigFileOfTheNewInstance';
Query OK, 0 rows affected (0.00 sec)

And with

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

Could this be part of the problem? I know the database exists but perhaps not connected?

Thanks!

jota 2017-04-27 07:50:25 UTC #19

Hi @jeffrey_veffer,

Just to confirm that everything was set properly, could you please try to access the database using the WordPress credentials? You will need to follow the next steps:

Check the wp-config.php file, this is the section in the instance I launched

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'bitnami_wordpress');

/** MySQL database username */
define('DB_USER', 'bn_wordpress');

/** MySQL database password */
define('DB_PASSWORD', '4f97e3982d');

Then, try to access the database with those credentials
```
mysql -u bn_wordpress -p4f97e3982d bitnami_wordpress
```

Can you access the database properly with those credentials? In case you got an error message, could you please share it with us?

If you can access the database, could you please share with me (jota [at] bitnami [dot] com) the content of the access_log, error_log of Apache and the log file of MySQL?

https://docs.bitnami.com/bch/components/mysql/#how-to-debug-errors-in-your-database
https://docs.bitnami.com/bch/components/apache/#how-to-debug-apache-errors

Regards,
Jota

jeffrey_veffer 2017-04-27 14:58:54 UTC #20

i am not sure if you created another database on the instance because I can't access using the credentials above.
There is something strange with the server - I can't access it using phpmyadmin.
I run this command

ssh -N -L 8888:127.0.0.1:80 -i KEYFILE bitnami@SERVER-IP

Then try to log in as before at
http://127.0.0.1:8888/phpmyadmin

But the server doesn't respond - it just keeps spinning. Should we create another instance?
[By the way, if Bitnami created an automated service to spin up a new WP Multisite instance and migrate from the old server to the new one I would buy it for sure!!!]

Thanks!

jota 2017-04-27 16:18:05 UTC #21

Hi @jeffrey_veffer,

My latest post was an example of the steps you'd need to perform, could you check the password in your wp-config.php file (/opt/bitnami/apps/wordpress/htdocs/wp-config.php)?

After that, could you please check that you can access the database using that password? I posted my command in the post, you'd need to modify the password after the -p option.

When creating the tunnel, what is the Operating System you're using locally? Could you please share with us the output of the same command but using "-vvvvvv" at the end of the command?

Regards,
Jota

Powered by Discourse, best viewed with JavaScript enabled

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!

SugarCRM

Drupal

WordPress

Joomla!

Redmine