Notices by Bajax (bajax@froth.zone)
-
Embed this notice
@lina @MK2boogaloo deep future cyberpunk shit but with like occult themes as well like SMT that'll be cool
-
Embed this notice
@MK2boogaloo @lina dude you're jumping way ahead we're only up to jajax last I checked you're skipping a bunch of letters
-
Embed this notice
@lina I know it is nuts
-
Embed this notice
@i @prettygood not really sure of the implications of that but I'll assume it's camaraderie and not "holy shit you dumbass"
-
Embed this notice
@prettygood God doesn't want me to have a pleroma instance. I get it.
-
Embed this notice
@prettygood trying to get it out of my house
-
Embed this notice
@prettygood I am so drunk I am probably scaring this thing way more than is necessary
-
Embed this notice
and ajax picks this as a wonderufl time to bring a living, screaming, angry SQUIRREL into my house
-
Embed this notice
I hosed my fucking instance again
-
Embed this notice
@vitalis any combat significance?
-
Embed this notice
@mint @pwm @i yeah obviously it was the other configs... I was so sure I didn't edit one of them by mistake lol
one grep -R could have prevented this
-
Embed this notice
@mint @pwm Yeah, I wouldn't have touched that (I don't even think there's a GUI control for it anywhere in the UI proper)
-
Embed this notice
@i @pwm @mint only an unintelligible (probably serialized) "instance" entry. I deleted it for good measure and restarted, still not working
-
Embed this notice
@i @mint @pwm restoring from backup did not fix it.
is it possible the remote instances have somehow auto blocked me because the way I query changed? this is such a bizarre error
-
Embed this notice
@i @pwm @mint `config :pleroma, :http, proxy_url: nil`
this should disable proxy entirely right?
-
Embed this notice
@pwm rofl still can't make it work... So now pleroma just plain can't send ANYTHING to ANYONE, even if I completely disable the outbound proxy in its config (is it maybe keeping some config directive around in the database? fuck!) the proxy works normally testing it with curl, but my instance just throws a whole mess of this shit in its logs whenever I make a post:
holy shit what have I done?
-
Embed this notice
just completely fucked up my instance trying to set up an outbound proxy... now pleroma gets econnrefused on every external query. I still get notifications, but anything initiated from my end just gives nothing. this persists even when I try to disable the proxy entirely in the pleroma config (pleroma.secret.exs). I've also disabled config from database. Anyone have any idea what's going on? Anyone know a way to figure out wtf pleroma is even trying to do that it's just completely lobotomized like this?
Statistics
- User ID
- 367991
- Member since
- 22 Oct 2025
- Notices
- 17
- Daily average
- 1