New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cant establish connection to wamp with autobahn! #555
Comments
What does the Network tab in debug tools show? Try making a basic WebSocket connection, does that connect? |
According the search I did among issues, I should use autobahn 0.8.* since it doesnt support wamp v2. I could not install that version via npm. The problem was probably this. I solved it by using thruway. Thanks. |
Yes it is, I do so. Autobahn 0.9+ implements wampv2, we have to use autobahn 0.8, and I also don't find it on npm. Instead I find wamp1, but I haven't tested it yet. |
Hi - Might I suggest putting some sort of disclaimer on the bottom of the push demo page? One's natural tendency when working with Javascript these days is to reach for libraries via npm. I personally wasted a good two hours trying to figure this out yesterday... |
Hi, I have seriously been trying for days to get this stuff working, using different autobahns and ratchet php and thruway. Does anyone have a complete example of this? :) |
@topproto If you use Thruway, use https://github.com/voryx/Thruway.js/ with it. Ratchet, when used with autobahn expects a version that supports WAMPv1, IIRC the current versions only support WAMPv2 at this point. |
I want to use use RPC via autobahn to my ratchet wamp server. But i could not establish the connection.
My server side:
My Class:
And the client side:
Here what i get from autobahn console.log:
unreachable
{ reason: null,
message: null,
retry_delay: 1.7760546390824472,
retry_count: 1,
will_retry: true }
unreachable
{ reason: null,
message: null,
retry_delay: 2.883934737974839,
retry_count: 2,
will_retry: true }
and what i get from serve side console output
opened close opened close
Anyone can help???
The text was updated successfully, but these errors were encountered: