Conversation

Notices

1. meso (meso@asbestos.cafe)'s status on Monday, 05-Jun-2023 22:11:57 JST meso

   • 7666
   uh oh what did i fuck up this time cc @7666 :marseyretard2:
   image.png
   • Machismo repeated this.
   • meso (meso@asbestos.cafe)'s status on Monday, 05-Jun-2023 22:11:55 JST meso

     in reply to

     • 7666
     @7666 it used to work fine not sure what changed in my config. I momentarily removed the asbestos.cafe entry from the hosts file, I *think* thats what might have triggered it, I put it back in there and it's still like this, not sure how that could have happened
     image.png
   • meso (meso@asbestos.cafe)'s status on Monday, 05-Jun-2023 22:11:56 JST meso

     in reply to

     • 7666
     @7666 they dont look like much is happening
     image.png
     Machismo repeated this.
   • 7666 (7666@comp.lain.la)'s status on Monday, 05-Jun-2023 22:11:57 JST 7666

     in reply to
     @meso Strange! you have a redirect loop somewhere somehow. Here's my proxy config that works with my instance, i don't think it's on my end but I made a change to proxying .well-known (different bug) - check your nginx logs for more details
     
     https://ghostbin.lain.la/paste/ze28x
     Machismo repeated this.
   • Tij (tij@boymoder.biz)'s status on Monday, 05-Jun-2023 22:13:10 JST Tij

     in reply to

     • 7666
     @meso @7666 so what theres asbestos.cafe and now theres THE asbestos.cafe?
   • meso (meso@asbestos.cafe)'s status on Monday, 05-Jun-2023 22:13:12 JST meso

     in reply to

     • 7666
     • Tij
     @Tij @7666 yeah
   • Machismo (zerglingman@freespeechextremist.com)'s status on Monday, 05-Jun-2023 22:14:00 JST Machismo

     in reply to

     • 7666
     @meso @7666 lmao what did you do
     post your nginx -T