[BUG] StreamingAPI disconnect after some time #203

Closed
opened 2022-11-11 17:09:33 +00:00 by YokaiRick · 5 comments

I have a problem with the streaming api. it seems to disconnect after some time. Therfore now new posts gets loaded until i hit refresh.

I currently run on 251e440dad
The error i get in the browser console is that it disconnects with status 1001.
See screenshot for more info.

Nothing seems to be of in akkoma-server logs.

When you disable the 'fetch posts in real time' option everything works fine

If you need more info just ping me :)

I have a problem with the streaming api. it seems to disconnect after some time. Therfore now new posts gets loaded until i hit refresh. I currently run on 251e440dad95ff0b46f42561d51ad82aa406ee7d The error i get in the browser console is that it disconnects with status 1001. See screenshot for more info. Nothing seems to be of in akkoma-server logs. When you disable the 'fetch posts in real time' option everything works fine If you need more info just ping me :)
Mergan added the
Bug
label 2022-11-17 23:12:48 +00:00

(1001) Indicates an endpoint is being removed. Either the server or client will become unavailable.

hm, which browser do you use? this could caused by client and server which is fun

>(1001) Indicates an endpoint is being removed. Either the server or client will become unavailable. hm, which browser do you use? this could caused by client _and_ server which is fun

oh this could ALSO be your webserver - are you proxying through nginx?

oh this could _ALSO_ be your webserver - are you proxying through nginx?
Author

oh sory, didn't saw you replied.
i run latest firefox 107.0-1 and yeah i proxy nginx

did the nginx conig changed recently?

oh sory, didn't saw you replied. i run latest firefox 107.0-1 and yeah i proxy nginx did the nginx conig changed recently?

it shouldn't have - but you might want to see if you've got any proxy timeouts on your nginx config (or nginx errors in the log or anything)

it shouldn't have - but you might want to see if you've got any proxy timeouts on your nginx config (or nginx errors in the log or anything)
Author

Finally had time to check out the logs.
I don't see anything suspicious in nginx logs either.. well.. when i enable streaming api, logs like these disappear, but i think this is just the old TL pulling without the websocket:

GET /api/v1/timelines/home?since_id=AQyhTeuBFQXdkctTE0&with_muted=true&reply_visibility=following&limit=20

I couldn't find any other requests regarding websockets or any specific api request.
Nothing is in nginx error logs either.

For me it looks like the websocket just dies after a few minutes and thats it.

But tbh, if i am the only person experience the problem, you can close the issue in my opinion.. i can live with the old pulling ^^

Finally had time to check out the logs. I don't see anything suspicious in nginx logs either.. well.. when i enable streaming api, logs like these disappear, but i think this is just the old TL pulling without the websocket: ``` GET /api/v1/timelines/home?since_id=AQyhTeuBFQXdkctTE0&with_muted=true&reply_visibility=following&limit=20 ``` I couldn't find any other requests regarding websockets or any specific api request. Nothing is in nginx error logs either. For me it looks like the websocket just dies after a few minutes and thats it. But tbh, if i am the only person experience the problem, you can close the issue in my opinion.. i can live with the old pulling ^^
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 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-fe#203
No description provided.