error trying to connect to node/socket.io server

[pkyeck]

i'm using node 0.50-pre and socket.io 0.7.2 and i'm getting the following error when trying to connect to my server.

client-side error:
Opening ws://MYURL:3000/socket.io/websocket
Connection failed with error: The operation couldn’t be completed. (WebSocketErrorDomain error 1.)

server is logging:
warn - unknown transport: "undefined"

should this still work?!

[pkyeck]

downgraded to socket.io 0.6.17 and i can connect successfully ...
anyone an idea what changed between these two version?

[fpotter]

A bunch of stuff changed :-) 0.7 has support for channels within the same socket.io connection. Hoping to get some time soon to add 0.7 compatibility.

[jmonster]

+1 for updating this. i am currently researching ways to implement a project at work and having native iphone/android socket.io support would simplify things greatly!

[pkyeck]

i rewrote this a couple of days ago. you can find it here: https:/pkyeck/socket.IO-objc

[plivesey]

I'm still having trouble with this issue. pkyeck, did you intend to rewrite this code to fix this issue? I still can't get it to work with your code. I'm running socket.io version 1.0.15 and wanted to try downgrading to 0.6.17 but don't know the command to do this...any advice?

Also, it works when I run from my local machine: socket.io version 1.1.0-alpha-6 with http protocol, but doesn't work when I run it from the server I'm using with https protocol. Any suggestions dealing with https? That may be the problem...

[pkyeck]

there's a version that supports SSL: https:/leftbee/socket.IO-objc
i haven't tried my version since the 0.7-era but there are some that are using the class more regulary: https:/pkyeck/socket.IO-objc/network

[plivesey]

hmmm...doesn't seem to work because websocket doesn't support wss. Do you know if theres a websocket library which supports wss and would work with this? I presume there has to be one, but leftbee doesn't seem so specify it and he's not available to message.

[dmportella]

getting the same error here but using the flash socket transport
any way to resolve the issue?

[plivesey]

So are you using wss (secure protocol)? If so, as far as I have found, there is no solution on github. If you need that as a solution, you'll need to do some coding yourself.

On Feb 1, 2012, at 4:00 AM, Daniel Portella wrote:

getting the same error here but using the flash socket transport
any way to resolve the issue?

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[dmportella]

I was using ws, seems i had some amazon security group blocking port 843. now it is open all is working