Plume takes much time to load and ends up throwing 503 #784

New issue

Open

opened 2020-06-18 15:00:58 +00:00 by verymilan · 0 comments

verymilan commented

2020-06-18 15:00:58 +00:00

(Migrated from github.com)

According to the Plume Matrix room, this is a known issue and is currently advised to workaround with automated restarts.

(if your instance is suffering from this, a @hourly restart of the Plume-service should do the trick)

However, it should be part of the issue tracker. :)

I am using Debian and Nginx.

On a fresh install, following the documentation and using the precompiled alpha-release, Plume starts throwing a 503 after a while, which seems to stay this way until Plume gets restarted. The first time i noticed that, was after my first remote-follow. According to the Plume Matrix room, this is a known issue and is currently advised to workaround with automated restarts. *(if your instance is suffering from this, a `@hourly` restart of the Plume-service should do the trick)* However, it should be part of the issue tracker. :) I am using Debian and Nginx.

👍 1

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#784

No description provided.

Rows
Columns