CONNECTION_REFUSED is standard when the port is closed, but it could be rejected because SSL is failing authentication (one of a billion reasons). Did you configure SSL with Ratchet? (Apache is bypassed) Did you try without SSL in JavaScript?
I don’t think Ratchet has built-in support for SSL. But even if it does you’ll want to try the ws:// protocol first; it’s a lot simpler, easier to debug, and closer to telnet. Chrome or the socket service may also be generating the REFUSED error if the service doesn’t support SSL (because you explicitly requested SSL).
However the refused message is likely a server side problem, (usually port closed).