Categories
Uncategorized

WP reroll

it turns out that something broke and I didn’t have a backup!

My web Server login page failed to load. There was nothing I can do to recover or restart the login page without deep diving into the code or a plug in that broke it. Either Jetpack, Woocommerce or an update, broke the login. I also did not have a backup, so I decided to reroll.

My renewed interest in bringing my site back was due to my upcoming wedding and the desire to create a passive income. The new site needs to be reliable and I need to find a way to quickly restore from catastrophic failures.

Site needs:

  1. Backup of all posts, daily.
  2. Backup of infrastructure, once.
  3. Quick load times.
  4. Minimal graphics.
  5. Mostly text based.
  6. Pocedure to reroll if necessary.

Things I did better:

  1. Rerolled into raspberry pi VM
  2. Copied and pasted posts
  3. Documented install and configure on Trello
  4. Left new pi VM on 80 and old broken on 443 to help transferring the posts.

The new site will run in a lightweight fashion on a Raspberry Pi through pfsense. This would allow me to monitor/manage the connections in and out. I placed configuration details on Trello and Google Drive so that i could get back into the system.

That evening I played a game and noticed extremely poor performance so I decided to quit the game. Windows needed an update so before I slept, I performed an update. I checked on the machine afterward and I could no longer see the VMs in HyperV. I also noticed that the RAM spikes to 98% as soon as you boot up, with nothing opened.

What fixed this?

The next morning I uninstalled the updates and was able to see the VMs. The new Pi VM was using dymanic memory. As soon ad I unchecked the box, ram dropped from 98% to 10%.

next steps:

  • Create backup of posts.
  • create backup of infrastructure.
  • rearrange pfsense.
    • cable modem, pfsense, router.
  • Add vlans to the network:
    • DMZ
    • IoT
    • Core
  • add to DMZ vlan:
    • Site
    • Fail2Ban
  • Migrate site from a windows VM to a PI.
  • Determine how to integrate https on Pi.
  • Turn off broken site.
  • Enable https on new Pi vm.
  • Add blog post.
  • SEO the blog post.

let’s see which I do next tonight…

Categories
Uncategorized

Bringing it back to life.

It has been some time since I last worked on my site. I returned to a broken site that would not load internally. I also:Could not find the current working configuration, the VM passwords or any details to easily fix the box.The current Configuration is saved to SmallPC documents as “Current Configuration W10.doc” From this file I needed the export password for my key.The VM username and password was saved to a text document in: download > personal > home lab > Web Server.The last files I needed was the routine to get the certificate updated which was saved in Two places: a text file with a specific process on W10web documents > “2021102 SSL Certificate build notes.txt.” The screenshots were saved to small PC > pictures > 20220324 Certificate renewal.I followed the routine in SSL Certificate build notes and was able to get the site up and running again over https.Also, I wiped the router recently and needed to re-enable port forwarding.While my documentation saved time, it still needs to be easier.

September 1, 2022 wp_writer