Reloading Elk is required to see my newly posted content

akaregi commented 11 months ago

Description

When I compose a new post and send it to the server, the server will process it but Elk won't show its post. To review the post, I need to reload Elk.

I don't know if this is Elk-side problem or other-side one.

Behavior

Expected:

New post will be shown in the timeline.

Actual:

Posting itself will be done
New post won't shown, need to reload to review the post.

System info

Environment:

I use GoToSocial (v0.11.1 Slightly Sloppier Sloth) as backend and Elk(elk.zone) as frontend.
I use Traefik for the reverse proxy of GTS.
Traefik and GTS run on Docker.
go.ecarlate.app is my GTS instance.

Error (Outputs from DevTools console):

entry.3481dbe8.js:8  WebSocket connection to 'wss://go.ecarlate.app/api/v1/streaming?stream=user' failed: 
(anonymous) @ entry.3481dbe8.js:8
connect @ entry.3481dbe8.js:8
stream @ entry.3481dbe8.js:8
streamUser @ entry.3481dbe8.js:8
r.value @ entry.3481dbe8.js:8
v @ notification.b15faa75.js:1
home:1

Uncaught (in promise) Event {isTrusted: true, type: 'error', target: WebSocket, currentTarget: WebSocket, eventPhase: 0, …}

System behavior:

According to logs, GTS receives WebSocket messages correctly but it returns 401 Unauthorized.

Other info

I use Elk on both elk.zone and main.elk.zone but the result is same.
GTS works fine on alternative frontends such as Semaphore. Semaphore shows the content immediately when posted.

illfygli commented 2 months ago

I have the same issue. I noticed that the request contains an access token on Semaphore:

wss://a.gts.instance/api/v1/streaming?stream=user&access_token=TOKENSTUFFZ5QAQKKMUTN5P4SKTEF5PRMQMSCH742MXVCQQ

But not on Elk:

wss://a.gts.instance/api/v1/streaming

Comparing the request headers, it looks as if Elk is sending the access token in a Sec-Websocket-Protocol header instead.

illfygli commented 2 months ago

Might get fixed on the GtS end soon: https://github.com/superseriousbusiness/gotosocial/pull/3169

shuuji3 commented 1 month ago

The above PR was merged recently so it should be available on snapshot releases. It would be helpful if someone using the snapshot version can confirm this issue was also fixed. 🙂

akaregi commented 1 month ago

Thank you for updates! Unfortunately, I couldn't confirm that the problem is fixed.However, the error like WebSocket connection to 'wss://go.ecarlate.app/api/v1/streaming?stream=user' failed: has been disappeared.

Tested in:

Elk v0.14.0 (as is elk.zone)
GoToSocial 3.5.3+0.16.1-SNAPSHOT+git-0a15555

This may be my deployment problem (I've changed the base from Docker to K8S), so I hope someone will test if the problem still exists too.

elk-zone / elk