{"id":663,"date":"2019-08-26T16:19:18","date_gmt":"2019-08-26T21:19:18","guid":{"rendered":"http:\/\/zewwy.ca\/?p=663"},"modified":"2019-11-26T20:40:44","modified_gmt":"2019-11-27T02:40:44","slug":"migrating-wordpress","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2019\/08\/26\/migrating-wordpress\/","title":{"rendered":"Migrating WordPress"},"content":{"rendered":"
\n

<\/span>The Story<\/strong><\/span><\/span><\/h1>\n<\/header>\n
\n

In the beginning, there was a man! This man ran! This man ran a site, it was awww inspiring, and so unknown. It ran on Linux in many forms, then one day it realized!!!!!!!! Everything becomes out of date!<\/p>\n

Ahem, anyway\u2026<\/p>\n

<\/span>Reasons for migrating<\/span><\/span><\/h2>\n

Whatever the reason maybe, mine happens to be this little gem right here:<\/p>\n

\"\"<\/a><\/p>\n

I\u2019m sorry\u2026 did that just say insecure\u2026 me\u2026 insecure\u2026<\/p>\n

OK, sometimes I can be a little insecure but you didn\u2019t have to shove it in my face. Anyway, whatever your reason for migrating maybe. I haven\u2019t done, and maybe you haven\u2019t either. So lets do this\u2026 together!<\/p>\n

Yeah\u2026 I googled\u2026 This was my main source, so big thanks to Tom Ewer for this write up<\/a> much like his mine will be rather indepth and manual. If you wish to avoid learning the nitty gritty and just want to get it done, or use a plugin to help see wpbeginner site here<\/a> they use a plugin called duplicator<\/a> and seems to have solid reviews. Since I\u2019m not a fan of paid magic, I\u2019m gonna do this manually.<\/p>\n

<\/span>Migrating WordPress<\/span><\/span><\/h1>\n

<\/span>Step 1 \u2013 Backup<\/span><\/span><\/h2>\n

Make sure you have a backup of your WordPress Server, in my case since they are VMs, I used Veeam to create a backup of my current WordPress server. Sadly even after logging in to the hosting VM and updating the repos and host OS (Debain 8 Jessie), this version of Debian ran out of support and thus it\u2019s repos weren\u2019t able to supply the updated PHP libraries needed to clear the alert.<\/p>\n

After that backup I followed along with Toms blog and instead of FTP (File Transfer Protocol) I used SCP (Yeah\u2026 I\u2019m NOT insecure! :P) WinSCP that is, what this actually means I\u2019m not sure apparently either Secure Contain Protect or Special Containment Procedures<\/a>, but under the hood it just uses SSH? Oh\u2026 \u201cSecure Copy (SCP)<\/a> is method of transferring files between computers over a secure channel. It uses the SSH protocol to do so\u201d<\/p>\n

In my case since it was Turnkey Linux, the web files were located at \/var\/www<\/p>\n

\"\"<\/a><\/p>\n

<\/span>Step 2 \u2013 Export WP Database<\/span><\/span><\/h2>\n

Now Tom ended up using phpMyADmin in his example, I wasn\u2019t sure if the Turnkey image I deployed was using the same, turns out after a quick google search and right on the VMs console, states Adminer on port 12322<\/p>\n

\"\"<\/a><\/p>\n

after login\u2026<\/p>\n

\"\"<\/a>Export\u2026.<\/p>\n

\"\"<\/a>Left all the default selections\u2026. then\u2026 what the\u2026.<\/p>\n

\"\"<\/a><\/p>\n

I was expecting a file to save, so instead I had to select all and save it to a file with Notepad++, all this was, was an output of the DBs in raw SQL.<\/p>\n

<\/span>Step 3 \u2013 Create DB Instances<\/span><\/span><\/h2>\n

Create your new DB instances, depending on how the SQL server handles DBs imports creation of actual DB\u2019s and their tables may very.<\/p>\n

<\/span>Step 4 \u2013 Verify DB Login Credentials<\/span><\/span><\/h2>\n

From the backup files in step 1, look in config.php for the DB user connection strings. Verify this user has a login and has proper access rights to the DB\u2019s and Tables being imported.<\/p>\n

Now\u2026.<\/p>\n

<\/span>What happened to me<\/span><\/span><\/h2>\n

Now in my case I simply spun up a new TurnKey WordPress server to see if they were maintaining their images, and sure enough this new was running on Debian 9 Strech, which is the recommended version. So from here although the Adminer version is the same @ 4.2.5 it looks different. Another thing to note was on the old version I was able to login to Adminer with \u2018root\u2019 on the new Adminer I had to login in with \u2018adminer\u2019.<\/p>\n

Now Tom states to create the Databases, I\u2019m not sure if he means the instances here, cause in my case it turns out the creation of the databases happens at import. So what happened to me was this.. first I tried to import\u2026<\/p>\n

\"\"<\/a><\/p>\n

Then he says to edit the config.php in my case since it was all default WordPress I figured, meh hopefully it\u2019ll all match.. hahah so I skipped his Step 4, also skipped his step 5 cause I already did that, as I said the creation of the DBs happens at import, at least if they don\u2019t already exist like the above error. In my case it just stated it for mysql, but not wordpress so I assumed the other 4 successful queries were for my wordpress data (hahah so many assumed mistakes).<\/p>\n

So I uploaded those unedited web files back to the same dir on the new server\u2026.<\/p>\n

\"\"<\/a><\/p>\n

and\u2026.<\/p>\n

\"\"<\/a><\/p>\n

DOH! hahaha That\u2019s why you don\u2019t skip Tom\u2019s Step 4, but in my case I had no interest in creating these as they should already exist, at least unless the WordPress image has changed that (in this case so lucky, they didn\u2019t) so all I had to do was figure out how to set the wordpress users password on the new DB to match that which is in the config.php\u2026. so I opened config.php grabbed the wordpress users password, and found out about this trick by James Goodwin<\/a>\u2026 \ud83d\ude00<\/p>\n

\"\"<\/a><\/p>\n

However, I was able to load my new WordPress site, but it was still the default one, not mine with my posts, themes, plugins\u2026 what the\u2026 which brought me back to my \u201cfailed\u201d DB import\u2026.<\/p>\n

When WordPress gives you attitude you drop em like their hot, drop em like their hot\u2026. but in this case WordPress is hot is I won\u2019t drop it, but I will drop those useless databases So, since this was all just a test server anyway, I went back into the Adminer on the new server and simple selected both MySQL, and wordpress and clicked the drop button.<\/p>\n

Then back into import, selected the same export SQL file\u2026 and\u2026<\/p>\n

\"\"<\/a>and sure enough my site loaded with all my content, all my plugins, all my posts, and no more PHP warning!<\/p>\n

<\/span>Summary<\/span><\/span><\/h1>\n

Now this covers the manual work to move WordPress, however much like what Tom covered, the final touches of how the site is accessed (direct NAT, behind load balancers, etc) are all on you in order to complete the migration for public access.<\/p>\n

In my case I\u2019ll probably prepare this new VM with the exact same Private IP information just on a separate vSwitch, once it\u2019s verified working 100% shutdown the old VM, swap the vSwitch connection to production, test, if good, delete old VM, if not change vSwitch ports and bring up old server.<\/p>\n

Worse case delete both VMs, restore my original server from my Veeam backups.<\/p>\n

*NOTE* I did experience one issue were I was unable to update WordPress or plugins after the migration. Turns out many posts point to the File System permissions<\/a> (which I suspected) I checked my old WordPress instance vs my new one and noticed all the files under the physical path had different owner and grp (root on new vs www-data on old) so…<\/p>\n

chown -R www-data:www-data \/path\/to\/wordpress<\/pre>\n
After that updates worked without issue.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
The Story In the beginning, there was a man! This man ran! This man ran a site, it was awww inspiring, and so unknown. It ran on Linux in many forms, then one day it realized!!!!!!!! Everything becomes out of date! Ahem, anyway\u2026 Reasons for migrating Whatever the reason maybe, mine happens to be this … <\/p>\n
Continue reading “Migrating WordPress”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[8,223],"tags":[225,224,45,56],"class_list":["post-663","post","type-post","status-publish","format-standard","hentry","category-server-administration","category-wordpress","tag-manual","tag-migrate","tag-migration","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=663"}],"version-history":[{"count":5,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/663\/revisions"}],"predecessor-version":[{"id":772,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/663\/revisions\/772"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}