Websockets don't work past v8.5.x

[TVGG]

Websockets don't seem to work properly as of version 8.5.x.

All websocket routes appear as route '[object Object]'
When trying to connect via wscat the following happens:

(base) C:\Users\marti> wscat -c localhost:3001
error: Unexpected server response: 502

Example route:

functions:
  defaultMessage:
    handler: src/socketFunctions/invalidRoute.main 
    timeout: 30
    events:
        - websocket:
            route: $default

• serverless version: 3.16.0
• serverless-offline version: 8.5.0
• node.js version: 14.16.0
• OS: win 10 build 19044.1645

It might be related to issue #1381

[inuwyze]

i have been having the same issue have u found any way around the problem?

[TVGG]

@qwtfy For the moment there doesn't seem to be a solution other than installing a previous version. 8.4 seems to work fine for my needs. In my experience serverless offline releases can be pretty buggy and have issues on one operating system but not another. I have tested 8.4 and it works well enough on windows for my needs but may have issues on mac os/linux.

[SayefReyadh]

For our project
v8.5.0 works with

serverless version: 2.52.0
node.js version: 12.13.0 / 12.x

v8.3.1 seems to also work fine along with v8.4.0 for

serverless version: 3.16.0
node.js version: 14.13.0 / 14.x

[aardvarkk]

I ran into this issue because I had a websocket authorizer set up, but wasn't returning a context on the policy. A workaround was to just return an empty object as the context on the policy. See #1472

[TVGG]

@aardvarkk Unless I am misunderstanding something I don't believe it's the same issue. In my specific case I do not use any authorizer. Would you have an example function like I provided in my original post so that I can test?

[aardvarkk]

@TVGG If you're not using an authorizer then this wouldn't be the same issue. Just thought I'd add a comment in here to help people that are using one because it "broke" websockets for me until I made that PR to fix the issue.

[TVGG]

@aardvarkk Thanks for the clarification!

[dnalborczyk]

#1381 was reverted in v8.8.0. could you check if your issue is gone?

If you're not using an authorizer then this wouldn't be the same issue.

it's possible that this is the same issue as that's how the handlers are run.

[TVGG]

@dnalborczyk The problem is still unresolved for the following config

serverless version: 3.16.0
serverless-offline version: 8.8.0
node.js version: 14.16.0
OS: win 10 build 19044.1706

I have updated windows 10 since the initial post but considering the issue was my serverless-offline version last time it seems that the problem is still persists in v8.8.0.

[dnalborczyk]

@TVGG v9 is going out the door in the next coming days. it contains some general bug fixes as well as some specific targeting Windows.

#1461

[dnalborczyk]

v9 was released a couple days ago. could you check if that takes care of the problem(s)?

I'm closing this issue in the meanwhile as I believe there's multiple issues bing conflated.

please open a new issue if the problem still persists.