rk1ve

casa-os-migration

the goal is to migrate remaining services off of the casa os vm. currently it is running three critical services; adguard home, omada controller, and nginx proxy manager. these are the backbone of my network and i have been putting it off to migrate them to their separate services. my first migration was uptime kuma as i can migrate that at anytime without much effect on my network. i attempted a backup and restore method, but that failed. so my options were either to just spin up a new instance again or look for a new solution. i decided on a hybrid since i still like the monitoring features of uptime kuma, and wanted to see other options.

i will most likely have to stand up another lxc with the uptime kuma install script and configure it manually. i tried solutions like checkmk and peekaping, but i decided to go with gatus. with these two monitoring solution i decided to keep gatus on the public front and uptime kuma on the internal side. i liked the advanced features and monitoring of web services on the gatus platform, so i decided to use it as a public facing status page for my websites. there was an install script for proxmox and deployed that, the configuration is through yaml and was pretty straight forward to setup. i have discord alerting with a webhook to my personal server. i might setup smtp, but for now discord will do.

next migration is the omada controller which was alright. the first migration attempt failed as the site migration requires the same controller version. and there seemed to be a bit of work to migrate from v5 to v6. until i realized that i could just do a controller migration, so i just did that and it worked flawlessly. i downloaded the controller config file and uploaded it to the new controller lxc. once it imported the site information, i just had to migrate all the devices to the new controller’s ip address. this process took a few minutes, and then an additional 15 minutes for the devices to fully configure with the controller. the migration was pretty seamless.

the third migration is adguard home, which should be pretty straight forward as well. i have not done it yet and will wait until later. i had to migrate the omada controller before adguard home since i wanted the new platform, but mainly so that i can change the dhcp scopes/information before the migration. i backed up the configuration of adguard home and will have to do the backup process. i have a lot of block lists setup and a few custom rules with lots of dns records.

the final migration would be nginx proxy manager. i have been considering switching to caddy, but i do enjoy the web gui of npm. the friendly nature is great, but it seems that caddy may be more performant, and does the same thing more or less. i have the nginx proxy manager files backed up and will have to research how that migration will go. otherwise, i might just do caddy as my reverse proxy. one thing i did in preparation was switch my proxy host dns records to cnames. that way it points to the host “proxy.domain.com” and i can just point that a record to the new ip address.

along with this local migration, i had to do a cloud migration as well. i might make it a different page.

preserve the moment.