vmware-archive / postfacto

Self-hosted retro tool aimed at helping remote teams
GNU Affero General Public License v3.0
8 stars 22 forks source link

WebSocket connection to 'wss://postfacto.[mydomain].de/cable' failed #435

Open vekngs opened 2 years ago

vekngs commented 2 years ago

I've deployed postfacto version 4.3.11 by using the official docker image.

Additionally I did the following:

Everything seems to be working just fine, but when checking dev-tools, I can see the error message shown in the attached screenshot.

Could any of you please tell me, what is causing this and if I can solve it?

Just let me know if you need more information :)

WebSocketConnectionFailed

aemengo commented 1 year ago

@vekngs Postfacto allows realtime updates, for when you're performing a retro remotely with your team. It allows this by connecting your client to your deployed server via websocket.

If you read the server logs, you'll see that it's currently failing. It should look like:

Started GET "/cable" for 127.0.0.1 at 2023-02-16 23:32:21 +0000
Started GET "/cable/" [WebSocket] for 127.0.0.1 at 2023-02-16 23:32:21 +0000
Request origin not allowed: https://postfacto.[mydomain].de        #<---- THIS VALUE
Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
Finished "/cable/" [WebSocket] for 127.0.0.1 at 2023-02-16 23:32:21 +0000
  1. "THIS VALUE" needs to be passed to the server via the CLIENT_ORIGIN: environment variable. If you're using helm it's not exposed, so I made PR: https://github.com/pivotal/postfacto/pull/465

  2. You also need to proxy the websocket connection through the nginx proxy.