Post B26pqH15TPgn3b8jp2 by elilla@transmom.love
 (DIR) More posts by elilla@transmom.love
 (DIR) Post #B26pq0pVegvAr3bGYS by elilla@transmom.love
       2026-01-08T23:34:13Z
       
       1 likes, 0 repeats
       
       > The server encountered an internal error and was unable to complete your request.Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.but doctorI *am* the server administrator :pinkgirl_cry:
       
 (DIR) Post #B26pq8e6ayYJ60KGtE by elilla@transmom.love
       2026-01-08T23:59:09Z
       
       0 likes, 0 repeats
       
       ok so apparently in bookworm at some point behind my back changed "redis", some web backend thing I couldn't care less about, to something else called "redict". there's not compatibility layer so that broke the server and socket paths, though the systemd service for "redis" was still trying to run, and failing silently. trying to run "redis" manually failed silently even with debug turned on. I needed to find some godforsaken hidden application-specific log file to figure out it was a tcp port conflict, which let me to find out about the existence of redict.and redict was not configured to make unix sockets, and anyway its path and group are all named "redict" rather than "redis", so of course the end result of that is that the nextcloud upon which I depend heavily suddenly breaks after midnight with a completely opaque error 500 and I have to be sleep deprived for tomorrow until I dig up all this.that's debian stable. the entire point is to not do things behind my back. what the hell happened here
       
 (DIR) Post #B26pqH15TPgn3b8jp2 by elilla@transmom.love
       2026-01-08T23:59:41Z
       
       0 likes, 0 repeats
       
       I don't hate software quite as much as I hate cops and nazis but swear to you, it's up there