I just spent the last couple of days trying to bring this site back online, after migrating it from a k8s server to a plain old docker container (You might have noticed how successful I had been by how long this site has been offline!). It’s finally back online, so it’s only fitting that after all that work, that at least I write a post about it.
Looking back, it’s actually rather simple, and I should’ve seen my folly sooner. Something in the back of my mind whispered this truth, but I obviously chose to ignore it. The original forwarded port was 30082, which I’ve been told (reliably?) that this is the range kubernetes things like to live at. Since I already had all sorts of rules in place to forward to that port, it only made sense to keep the port! What I did learn, finally, is that my reverse proxy did not like that port, and refused to work correctly with it. I went through numerous, NUMEROUS I SAY, failed attempts to bring my site back online and nothing worked. Dear reader, I was about to give up altogether.
So here we are, after another failed attempt to get reverse proxy working, when that sad voice spoke from the back of my mind one more time
And as you can see, because you are reading this words, that worked! I was able to not only bring the site back online, I was able to restore my backups too.
It’s been a long time since I’ve written anything, and writing now has been nice. Life has changed quite a bit since I last wrote (you have no idea how much!) and I’d love to take that back up again. Time will tell!