WSS Not working for some sites. about arduinowebsockets

[gilmaimon]

Thank you for the report, I was able to reproduce this bug on my side and can confirm it is a bug.
I will look into it and will post here any updates I'll have.

[gilmaimon]

@johneakin Great! I'm glad it's working now.
@bastienvans Did it work for you aswell?

[johneakin]

Many thanks
Seems to be working great.

[johneakin]

I am also looking this to work for
wss://ws-feed.gdax.com

[bastienvans]

I am also looking this to work for
wss://ws-feed.gdax.com

Their API URL has changed to ws-feed.pro.coinbase.com.

[bastienvans]

Thank you for the report, I was able to reproduce this bug on my side and can confirm it is a bug.
I will look into it and will post here any updates I'll have.

Thanks!

I got it to work using another code posted on github. I ended up using WiFiClientSecureBearSSL.

[johneakin]

Is that now working with a socket or just an HTTPS request?
Can you include the source code for connecting to wss://ws-feed.pro.coinbase.com

[gilmaimon]

Thank you for the report guys. I've fount at least one bug that had to do with the parsing of the server's response. For some reason, wss://ws-feed.pro.coinbase.com returns one header which is a-bit diffrent than standard.

The problem is still not fully solved, as I am able to make a connection with wss://ws-feed.pro.coinbase.com without it closing the connection immidiatly. Yet, the connection does not seem to be active (I was unable to receive any response from the server).

Communicating with wss://api.bitfinex.com/ws/2 works fine after the patch. By the end of the day there will be a patch live, hopefully it will solve both issues.

[gilmaimon]

Hi guys @bastienvans @johneakin

I believe the issue is now solved complely. Patch 0.4.1 is live!
It is available now via the release page and will be soon available for update via the Arduino IDE.

Thank you for reporting the issue and providing usefull information and logs. Please verify it is working for you properly.

[johneakin]

Thanks
I'll give it a try and report back

When you say completely solved, Do you mean also working for: wss://ws-feed.pro.coinbase.com
?

[johneakin]

wss://ws-feed.pro.coinbase.com is connecting and staying connected
but onMessageCallback doesn't appear to be getting called with new data which should be coming in regularly

[gilmaimon]

@johneakin Try adding a dummy send method and see if the you get the server's response. For me, adding send for "hello" in setup will return the message {"type":"error","message":"Malformed JSON","original":"hello"} immidiatly.
What kind of data you expect to get "regulary" from the socket? I've tried the connection on PC (with some downloaded websockets client) and the connection seems to disconnect after few seconds of inactivity.

[bastienvans]

@johneakin Try adding a dummy send method and see if the you get the server's response. For me, adding send for "hello" in setup will return the message {"type":"error","message":"Malformed JSON","original":"hello"} immidiatly.
What kind of data you expect to get "regulary" from the socket? I've tried the connection on PC (with some downloaded websockets client) and the connection seems to disconnect after few seconds of inactivity.

Yeah, you have to keep pinging it to stay connected.

[johneakin]

My fault, I wasn't sending the subscribe json

client.connect("wss://ws-feed.pro.coinbase.com");
client.send("{"type": "subscribe","product_ids": ["BTC-USD"],"channels": ["ticker"]}");

After I send that I get the frequent price updates in the: onMessageCallback

[gilmaimon]

Fantastic! Thank you guys for bringing up the issue.
Gil.

[imesut]

Hello,

I see the same issue while working with wss://stream.toggl.com/ws link.

This link receives authentication token then decides to continue or disconnect. But in every attempt, it disconnects immediately before sending token.

The patch also didn't worked for me. Any suggestions?

[gilmaimon]

Hello,

I see the same issue while working with wss://stream.toggl.com/ws link.

This link receives authentication token then decides to continue or disconnect. But in every attempt, it disconnects immediately before sending token.

The patch also didn't worked for me. Any suggestions?

Hi,

Are you sure it's the same issue? Open a new issue and I will look into it.

Gil

[imesut]

Hello,
I see the same issue while working with wss://stream.toggl.com/ws link.
This link receives authentication token then decides to continue or disconnect. But in every attempt, it disconnects immediately before sending token.
The patch also didn't worked for me. Any suggestions?

Hi,

Are you sure it's the same issue? Open a new issue and I will look into it.

Gil

Thanks, I've opened Issue 67