Migrate WordPress Blog

I wanted to move my WordPress blog to my Openmediavault server to consolidate my hardware. It use to be that I have this blog on a standalone FreeBSD box.

So what did I do to make this happen? Here are the high level steps that I did.

  1. Prepare the VM.
  2. Move the data.
  3. Run the App.
  • Openmediavault is able to run Docker and also KVM.

I decided to use KVM because I wanted familiarity and I have not have a lot of experience with docker containers. However, I was also successful in migrating my other applications into docker containers ( more on this to follow.)

  • Migrate the data.

I did a database export and copied over my /usr/local/etc and /usr/local/www folders. I imported the data using the mariadb commandline since I have not setup PhpMyAdmin yet. I encountered a snag on the import. It seems that my database will not import unless I did an individual export of the databases. Something to do with the database user conflicts. Another thing with the import is that I have to redo the database users. I had to drop the users, create user, grant privileges, and finally flush privileges.

The configs I had to check the users and groups as well as the root folder (www) and the wp-content.

  • Run the app.

It would have been simpler if I just setup the server the same way. But, I decided to add an NGINX reverse proxy into the mix. I am able to make it work somewhat but ran into an issue when logging into the app.

this is the error I got:

fatal error: uncaught error: call to undefined function ctype_digit() in /usr/local/www/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-signature.php:244 stack trace: #0 /usr/local/www/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(136): jetpack_signature->sign_request('i9a$fqo@pwxac&o…', 1578694208, 'ldozcjbmxi', 'vbvvpd3yni1/f2m…', 'post', 'https://jetpack…', 'query('jetpack.sso.req…') #3 /usr/local/www/wordpress/wp-content/plugins/jetpack/modules/sso.php(409): jetpack_sso::request_initial_nonce() #4 /usr/local/www/wordpress/wp-content/plugins/jetpack/modules/sso.php(392): jetpack_sso- in /usr/local/www/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-signature.php on line 244

I googled for days but I could never find any solution on the net. I finally decided to try to uninstall the Jetpack plugin. I had to go to wordpress.com and disconnect my blog. Once , I did that I was able to login. I then was able to update WordPress and re-enable the jetpack plugin. Booyah!!!

QEMU openmediavault

Installing QEMU VMs through Cockpit is not straightforward.
You still need additional configuration.

Here is the rough draft of what I did to get it working.

  1. setup bridge interface using standard linux setup.
  2. install brctl, dnsmasq, and ebtables.
  3. run virsh edit to modify the VNC port.

sources:

https://forum.openmediavault.org/index.php/Thread/26913-Cockpit-VirtMachine-Error/

https://forum.openmediavault.org/index.php/Thread/25143-Cockpit-Qemu-and-VirtMachine/

https://qemu.weilnetz.de/doc/qemu-doc.html

Spring cleaning/upgrade

Today I was doing a lot of upgrading.

I was able to purchase a new PC to get my pFsense install into the latest and greatest 2.4.3 version. My old router PC was an old Pentium 4 and pFSense needs a 64Bit CPU. I went ahead and got an old HP 8200 SFF which has a Core I5 CPU. At least, I am future proofing a bit when 2.5 comes up. I added a quad port NIC and I think I am set for now.

I had a small hiccup with the config restore because there was no easy way for one to tell which port is em0 or em1. Can’t really tell from looking at the connections and in the console. I guess one can do trial and error and move the connections and doing a ping. The only thing is after one reboots, the system will try to find an internet connection and one can’t really proceed. I found a bug report at the pFsense site which mentions a work around for this. Essentially, one has to disable the pkg source file so that one can skip to the console main screen. Took me about a good couple of hours troubleshooting.

Lastly, after I got my internet back and while I thought making a note of all of this in WP, I got another upgrade notification. All in a days work. Fun.