@ColonelPanic@lemmy.ml to Technology@beehaw.org • 1 year agoLemmy v0.18.0 Releasejoin-lemmy.orgmessage-square4fedilinkarrow-up144cross-posted to: switzerland@feddit.chsdfpubnix@lemmy.sdf.orgsupport@lemmy.nznews@lemmy.linuxuserspace.showfoss@beehaw.orgselfhosted@lemmy.worldsupport@beehaw.orgfeddituk@feddit.ukphilippines@lemmy.world
arrow-up144external-linkLemmy v0.18.0 Releasejoin-lemmy.org@ColonelPanic@lemmy.ml to Technology@beehaw.org • 1 year agomessage-square4fedilinkcross-posted to: switzerland@feddit.chsdfpubnix@lemmy.sdf.orgsupport@lemmy.nznews@lemmy.linuxuserspace.showfoss@beehaw.orgselfhosted@lemmy.worldsupport@beehaw.orgfeddituk@feddit.ukphilippines@lemmy.world
minus-squareMarduklinkfedilink4•1 year agoran into some weirdness after updating my private instance via ansible. Was getting lots of json errors and bad gateway errors along with occasional timeouts. Reverted to pre-upgrade snapshot for now.
minus-squarehoshikarakitaridialinkfedilink4•1 year agoDefinitely should put that on the git issues with log files and stuff.
ran into some weirdness after updating my private instance via ansible. Was getting lots of json errors and bad gateway errors along with occasional timeouts. Reverted to pre-upgrade snapshot for now.
Definitely should put that on the git issues with log files and stuff.