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

Kevoree behind proxy server #17

Closed
tdalianis opened this issue Jul 13, 2016 · 2 comments
Closed

Kevoree behind proxy server #17

tdalianis opened this issue Jul 13, 2016 · 2 comments
Assignees

Comments

@tdalianis
Copy link

Hi everyone,

I have a kevoree instance running on server of our internal network which is behind a proxy server.
When i access the instance from the editor using the internal ip, the kevoree model is shown at the editor, but when i am using the public domain name of the server i get the error "Unable to connect to ws://domainName:9000/".
At the same time at the kevoree logs i get "ERROR: WSGroup "sync": io.undertow.websockets.core.WebSocketFrameCorruptedException: UT002015: Extensions not allowed but received rsv of 4"

Have you made any tests involving a proxy server? Is there a configuration that can be done to resolve this issue?

Thank you for your time in advance.

@maxleiko maxleiko self-assigned this Jul 13, 2016
@manuelleduc
Copy link
Member

According to the answer of stuartwdouglas in this issue (Atmosphere/atmosphere#1550) the problem might be fixed with Undertow 1.0.4.Final

Currently the WSGroup is dependent of Undertow 1.2.0 (as a recursive dependency of fr.braindead:wsmsgbroker-client:1.0.6

I'm going to test if I can update the version of undertow.

I'll let you know how it goes as soon as possible.

PS : Tomorrow is a public holiday in France (bastille day) so basically no one at INRIA will work neither tomorrow not on Friday.

@maxleiko
Copy link
Member

Closing this as it is not really Kevoree-related.

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

3 participants