[bug] Error fetching timeline: Unexpected status: 502 #532

New Issue

Closed

opened 2023-04-30 11:01:13 +00:00 by creme · 1 comment

creme commented

2023-04-30 11:01:13 +00:00

hi, so there is something interesting. I tested everything possible yesterday. Everything worked until the loading of the "known network" timeline.

I optimize my postgresql config with https://pgtune.leopard.in.ua / , gave the machine more RAM and optimized the DB itself:

su pleroma -s $SHELL -lc "./bin/pleroma_ctl database prune_objects --keep-threads --keep-non-public --prune-orphaned-activities"
and
REINDEX (VERBOSE) DATABASE CONCURRENTLY pleroma;

this, at least, obviously, did not improve anything. The timeline still could not be loaded.

But when I log out now, I see the "known network" timeline as an visitor and it shows posts. But the public timeline looks near empty. Which, however, works in the logged-in state.

When I log in again as a user creme, all timelines load without problems and show me all posts and also newly arriving ones.
But as soon as I reload the tab in the browser (via F5) I get the error message "Error fetching timeline: Unexpected status: 502" again and the known network timeline does not load again :/

I can recreate the behavior with 3 accounts that I manage. Both in Firefox and in the google-chrome browser.

i test it with "rich_media" and "media_proxy" enabled and disabled. it makes no difference.

vistor view (public timeline):

visitor view (known network timeline):

fresh login view (known network):

reload tab (known network):

Originally posted by @creme in #487 (comment)

hi, so there is something interesting. I tested everything possible yesterday. Everything worked until the loading of the "known network" timeline. I optimize my postgresql config with https://pgtune.leopard.in.ua / , gave the machine more RAM and optimized the DB itself: `su pleroma -s $SHELL -lc "./bin/pleroma_ctl database prune_objects --keep-threads --keep-non-public --prune-orphaned-activities"` and `REINDEX (VERBOSE) DATABASE CONCURRENTLY pleroma;` this, at least, obviously, did not improve anything. The timeline still could not be loaded. But when I log out now, I see the "known network" timeline as an visitor and it shows posts. But the public timeline looks near empty. Which, however, works in the logged-in state. When I log in again as a user creme, all timelines load without problems and show me all posts and also newly arriving ones. But as soon as I reload the tab in the browser (via F5) I get the error message "Error fetching timeline: Unexpected status: 502" again and the known network timeline does not load again :/ I can recreate the behavior with 3 accounts that I manage. Both in Firefox and in the google-chrome browser. i test it with "rich_media" and "media_proxy" enabled and disabled. it makes no difference. vistor view (public timeline): ![image](/attachments/0f0ef0b1-9dde-46f5-a654-733955e1b70b) visitor view (known network timeline): ![image](/attachments/af02a3e9-c3fc-4f61-b148-1772d48d310d) fresh login view (known network): ![image](/attachments/9ea2a00c-da30-4859-974b-a0c404aef1d3) reload tab (known network): ![image](/attachments/5c045a85-6ac9-4463-bf4c-3a44e1b992d6) _Originally posted by @creme in https://akkoma.dev/AkkomaGang/akkoma/issues/487#issuecomment-7949_

creme commented

2023-08-05 22:03:09 +00:00

Author

the instance has healed by itself.

creme closed this issue

2023-08-05 22:03:10 +00:00

No Milestone

No project

No Assignees

1 Participants

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: AkkomaGang/akkoma#532

No description provided.