I borked the server that has been hosting my instance of nodestorage, which in turn provided the editing for my old 1999.io blog. This blog was the direct predecessor to this site and I was publishing to it from May 2016 to February 2018. Before that, from 2014 to April 2016 I was publishign to this site using Fargo.
Right now I cannot SSH in to the server but I do know that it is running and serving up an old Bitnomi default page. I decided to build a new server to replace it, but won’t be able to move any of the data on the old server if I cannot get in to it.
I had nodestorage configured to publish the content to a S3 bucket, which is serving it directly, so I was not expecting the outage to affect the published site, but it does. When you first access the top navigation bar is delayed in loading. Looking at the page source I see variables that contain URLS back to that old site, one which appears to be defining a chat log socket. Unfortunately, this means to not have this affect on the old blog content I need to keep nodestorage running at the URL provided.
from Frankly… https://ift.tt/3kI9hOj
via IFTTT
Notes From The Cave 
Leave a Reply