{"id":1219,"date":"2024-09-29T13:50:41","date_gmt":"2024-09-29T16:20:41","guid":{"rendered":"https:\/\/blog.pelleys.com\/?p=1219"},"modified":"2024-09-29T13:50:41","modified_gmt":"2024-09-29T16:20:41","slug":"vps-in-place-release-upgrade-gone-wrong","status":"publish","type":"post","link":"https:\/\/blog.pelleys.com\/?p=1219","title":{"rendered":"VPS In-Place Release Upgrade Gone Wrong"},"content":{"rendered":"\n<p>On Thursday night, about an hour before going to bed, I decided to do an in-place upgrade to my VPS. I knew I had good backups of WordPress, the websites, etc. so I was not all that concerned. I have done many, many release upgrades of Ubuntu on-site I figured about 30-40 minutes for the upgrade. And indeed, after about 30 minutes the upgrade was finished and it was time to reboot.<\/p>\n\n\n\n<p>I gave the VPS about a minute to restart and&#8230; nothing. I could not connect using SSH or using a web browser. I hop onto the VPS console and see a bootloop. Ok, I&#8217;ve seen this happen before. Jump into recovery mode and see what was broken and fix it. And it seems I really broke something as I could not even start the recovery console. I have done a couple of in-place release upgrades plus, of course, a bunch of tweaks over the last few years so I can see that causing issues.<\/p>\n\n\n\n<p>Since I was tired I powered off the borked VPS and off to bed I went. I am finally old and wise enough (or maybe my ass was dragging&#8230;) to know being tired and being successful often does not work out.<\/p>\n\n\n\n<p>The next day I installed a new instance of the VPS and began the recovery.<\/p>\n\n\n\n<p>The good news:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The WordPress recovery went fairly easily. The database backup was solid. I just had to remember to create the WordPress database account and grant it access to the WordPress database. Funny about that&#8230;<\/li>\n\n\n\n<li>The recovery of the other websites went fine.<\/li>\n\n\n\n<li>It gave me a chance to clean up some of the php code, old URLs that had existed for who knows how long, etc.<\/li>\n\n\n\n<li>Re-implementing Let&#8217;s Encrypt SSL was buttery smooth.<\/li>\n\n\n\n<li>But, more details below&#8230;<\/li>\n<\/ul>\n\n\n\n<p>The bad news:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>I had meant to back up and copy offsite the WordPress content directory. I had part of it done &#8211; copy it it over to another directory &#8211; but I did not remember to set up the job to copy the contents offsite. Insert Homer Simpson Dunh! here. Then I remembered last month I was messing around with a <strong>full copy<\/strong> of my WordPress site locally. Awesome &#8211; I have a copy of the WordPress contents. Upload and fixed.<\/li>\n\n\n\n<li>I somehow did not have an anywhere near current copy of the other websites. That meant that other fixed that I had done over the years did not exist. However, it did mean I had the chance to update the php code.<\/li>\n\n\n\n<li>I also did not keep a copy of the ufw blocks for, shall we say, less than desirable ISPs. Backed up now and improved by cleanup.<\/li>\n<\/ul>\n\n\n\n<p>Lesson learned: Make sure your backups are <strong>complete<\/strong>. Don&#8217;t assume anything.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Thursday night, about an hour before going to bed, I decided to do an in-place upgrade to my VPS. I knew I had good backups of WordPress, the websites, etc. so I was not all that concerned. I have &hellip; <a href=\"https:\/\/blog.pelleys.com\/?p=1219\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1219","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/posts\/1219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1219"}],"version-history":[{"count":1,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/posts\/1219\/revisions"}],"predecessor-version":[{"id":1220,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=\/wp\/v2\/posts\/1219\/revisions\/1220"}],"wp:attachment":[{"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.pelleys.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}