Conversation

Notices

1.  (mint@ryona.agency)'s status on Monday, 14-Oct-2024 04:54:42 JST 

   in reply to

   • 0
   • pwm
   @pwm @0 I'd like to see the full error first.
   • 0 (https://pl.absolutelyproprietary.org/users/0)'s status on Monday, 14-Oct-2024 04:54:43 JST 0

     in reply to

     • 0
     • pwm
     @pwm Upping the Pleroma workers did not seem to help, so I am guessing it's an nginx issue, but also I don't want to presume that presentation is cause; i.e. the worker issue is symptomatic.
   • pwm (pwm@pl.absolutelyproprietary.org)'s status on Monday, 14-Oct-2024 04:54:43 JST pwm

     in reply to

     • 0
     @0 If you like I can take a look tomorrow, about to do a 7 hour shift.
     I have no bright ideas off the top of my head without poking at it. You might want to ask @mint if he has any bright ideas on where to start in the meantime.
   • 0 (https://pl.absolutelyproprietary.org/users/0)'s status on Monday, 14-Oct-2024 04:54:44 JST 0

     in reply to

     • pwm
     @pwm I need to solve these 500 errors. I am open to advice here, the error logs say "worker error" but I can't tell if it's nginx isssue, wg issue, or pleroma issue.
   • pwm (pwm@pl.absolutelyproprietary.org)'s status on Monday, 14-Oct-2024 04:54:45 JST pwm

     in reply to

     • 0
     @0 I want to follow.
   • 0 (https://pl.absolutelyproprietary.org/users/0)'s status on Monday, 14-Oct-2024 04:54:46 JST 0
     Considering doing the downgrade to 2.6.3 today.