I started playing with my key files in order to encrypt and secure them, I don’t want my ZeroNet account to fall in malevolent hands and I’m mainly referring to those of a thief.
I decrypted my keys into a folder and then sym-linked to zeronet/data so I started using the platform as usual without hassles… But starting from the second time I activated the service, after a reboot and forgot the first time to un-encrypt, something started to go wrong… indeed, I was unable to like stuff, comment and act as usual getting errors like this one directly on the GUI:
Internal error: Exception: Invalid content.json file
immediately followed by:
WebSocket handleRequest error: Exception: Invalid content.json file: data/users/(my auth_address)/data.json in UiWebsocket.py line 83 > UiWebsocket.py line 267 > MergerSitePlugin.py line 203 > MergerSitePlugin.py line 197 > UiWebsocket.py line 484 > MergerSitePlugin.py line 200 > MergerSitePlugin.py line 197 > UiWebsocketPlugin.py line 36 > UiWebsocket.py line 431
and I’ve found just now watching at the logs on the CLI, this:
Json merged-ZeroMe/(KaffieHub address)/data/users/(14ytAKDfNjArMTqGecTi7ginG3aZTsRAum)/content.json load error: DatabaseError: database disk image is malformed in SiteStorage.py line 299 > ContentFilterPlugin.py line 167 > SiteStorage.py line 90 > SiteStorage.py line 82 > Db.py line 166 > Db.py line 132 > Db.py line 65 > Db.py line 139 > DbCursor.py line 90
I’ve been a couple of days off because of this inability to operate as myself… I’ve tried to double check permissions, substituted keys with the previous ones from the backups, took searches, updated ZeroNet… until I remember that my ZeroNet data folder was on the periodic scheduler of
snapper, so I just run the command
btrfs -c (name of the config) undochange (oldsnapshot)..0 and everything came back to normal :)
So I must thank Open Suse’s snapper software for the success of my rescue mission! : )
This is how I’ve been able to handle the casualty! ^^ and I suggest you doing snapshots too, sometime unexpected things occur and these are a life saver :3
Oh… and in the meantime, I big failed in my attempt to save the blog draft and published as an empty post instead! as @leftside let me notice
just, I can’t recall hitting the Sign & Publish button, uhm… part of my odd experience? who knows :)
Ever happened something similar to any of you?
Have you wrote a blog about? If you did, I’d love to read about your experience and how you solved it! ^^