Skip to content
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

client can't connect to crossbar universal transport #77

Closed
keiser1080 opened this issue Nov 12, 2018 · 2 comments
Closed

client can't connect to crossbar universal transport #77

keiser1080 opened this issue Nov 12, 2018 · 2 comments

Comments

@keiser1080
Copy link

hi,
Crossbar v18.11.1 is shiped with a config template using universal transport.
I mean when you do crossbar init , a folder is created with a basic config & the certificats.
When wampy client try to connect crossbar try to reconise a websocket client
in basis of the first byte => what he call "the magic Raw Socket byte"

see here => https://crossbar.io/docs/Transport-Endpoints/ (search on this page for Universal Listening Endpoints)

2018-11-12T18:34:05+0100 [Router      21379 crossbar.router.unisocket.UniSocketServerProtocol] switching to HTTP on Request-URI //, mapping part 
2018-11-12T18:34:05+0100 [Router      21379 crossbar.router.unisocket.UniSocketServerProtocol] no mapping found for request URI //, trying to map part 
2018-11-12T18:34:05+0100 [Router      21379 crossbar.router.unisocket.UniSocketServerProtocol] client wants to talk HTTP/Web, but we have no factory configured for that
@keiser1080
Copy link
Author

keiser1080 commented Nov 13, 2018

update:

to connect to an universal endpoint we need to append '/ws' at the end of the uri
ex : ws://127.0.0.1:8080/ws
using this url i am able to connect .
the issue can be close

@keiser1080
Copy link
Author

i just found the close issue button

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant