search

sacOO7 / socketcluster-client-java

Native java and android client for socketcluster framework in node.js
http://socketcluster.io/
Apache License 2.0
94 stars 43 forks source link

can connect to wss (SSL) server #14

Closed cogmeta closed 7 years ago

cogmeta commented 7 years ago

Getting this error java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. while connecting to wss server. Can this client handle SSL connections? wss://----/socketcluster

sacOO7 commented 7 years ago

I think you can disable certificate verification?

On Sep 16, 2017 9:20 PM, "Cogmeta" notifications@github.com wrote:

Getting this error java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. while connecting to wss server. Can this client handle SSL connections? wss://----/socketcluster

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sacOO7/socketcluster-client-java/issues/14, or mute the thread https://github.com/notifications/unsubscribe-auth/AP8vSeH0YP8A-rV-FKYHa6wAJzzUhUVjks5si-5PgaJpZM4PZ24y .

cogmeta commented 7 years ago

Thank you. But disabling certificate verification is not an option. If missing certificate is the issue, we will add them and try again.

sacOO7 commented 7 years ago

Yes, you can do that :+1:

cogmeta commented 7 years ago

Can we ask for a favor? Can you please try connecting wss://----/socketcluster and let us know. Thanks in advance. I think we are able to connect to ws://---/socketcluster but there is no connect event on server.

sacOO7 commented 7 years ago

Ohk sure. I think you should test SSL certificate once again.

sacOO7 commented 7 years ago

And yes do star the client :P .

cogmeta commented 7 years ago

We got rid of the ssl certification verification error but we still don't see connect event on server. Can you help us please? Thanks.

PS: starred the repo.

sacOO7 commented 7 years ago

Thank you. Can you post your code here. Refer code at this repo. if possible https://github.com/sacOO7/LAN-chat-Web-App

cogmeta commented 7 years ago

Stepped into Socket.connect and there is OpeningHandshakeException exception: com.neovisionaries.ws.client.OpeningHandshakeException: The status code of opening handshake response is not '101 switching protocols'. The status line is: HTTP/1.1 400 URL not supported

sacOO7 commented 7 years ago

What is a URL?

On Sep 17, 2017 1:06 AM, "Cogmeta" notifications@github.com wrote:

Stepped into Socket.connect and there is OpeningHandshakeException exception: com.neovisionaries.ws.client.OpeningHandshakeException: The status code of opening handshake response is not '101 switching protocols'. The status line is: HTTP/1.1 400 URL not supported

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/sacOO7/socketcluster-client-java/issues/14#issuecomment-329990222, or mute the thread https://github.com/notifications/unsubscribe-auth/AP8vSU6OKAapkUtjw_j3-DW4ce8TY8Jiks5sjCNHgaJpZM4PZ24y .

sacOO7 commented 7 years ago

Did you tried my code? I have tested it and it should work without any problem

On Sep 17, 2017 1:07 AM, "Sachin Shinde" sachinshinde7676@gmail.com wrote:

What is a URL?

On Sep 17, 2017 1:06 AM, "Cogmeta" notifications@github.com wrote:

Stepped into Socket.connect and there is OpeningHandshakeException exception: com.neovisionaries.ws.client.OpeningHandshakeException: The status code of opening handshake response is not '101 switching protocols'. The status line is: HTTP/1.1 400 URL not supported

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/sacOO7/socketcluster-client-java/issues/14#issuecomment-329990222, or mute the thread https://github.com/notifications/unsubscribe-auth/AP8vSU6OKAapkUtjw_j3-DW4ce8TY8Jiks5sjCNHgaJpZM4PZ24y .

cogmeta commented 7 years ago

No luck so far in fixing this. URL not supported error. We tried both URLs wss://subdomain.domain.me/sockercluster and wss://subdomain.domain.me but same error. Our socketcluster server is running behind nginx. No access or error log entry in nginx logs. Works find with all web and mobile browsers.

/OpenGLRenderer: Initialized EGL, version 1.4 D/AbstractTracker: Event success I/io.github.sac.Socket: === Status Line === I/io.github.sac.Socket: HTTP Version = HTTP/1.1 I/io.github.sac.Socket: Status Code = 400 I/io.github.sac.Socket: Reason Phrase = URL not supported I/io.github.sac.Socket: === HTTP Headers ===

sacOO7 commented 7 years ago

I think cause might be URL. It's little different due to subdomain. Can you keep domain as www.websitename.com

On Sep 17, 2017 2:53 AM, "Cogmeta" notifications@github.com wrote:

No luck so far in fixing this. URL not supported error. We tried both URLs wss://subdomain.domain.me/sockercluster and wss://subdomain.domain.me but same error.

Our socketcluster is running behind nginx and it works fine with all browser clients.

/OpenGLRenderer: Initialized EGL, version 1.4 D/AbstractTracker: Event success I/io.github.sac.Socket: === Status Line === I/io.github.sac.Socket: HTTP Version = HTTP/1.1 I/io.github.sac.Socket: Status Code = 400 I/io.github.sac.Socket: Reason Phrase = URL not supported I/io.github.sac.Socket: === HTTP Headers ===

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sacOO7/socketcluster-client-java/issues/14#issuecomment-329995732, or mute the thread https://github.com/notifications/unsubscribe-auth/AP8vSSNMnZdBBDC2YhiycLhMFpU_0b9Xks5sjDxugaJpZM4PZ24y .

cogmeta commented 7 years ago

We will try and report back. But, it wont really solve our problem as we have multiple socketcluster services running under different subdomains.

cogmeta commented 7 years ago

Ok, wss://subdomain.domain.me/sockercluster/ [with trailing slash] works while wss://subdomain.domain.me/sockercluster does not. Most likely it is nginx issue. Will dig deeper and post more. Thanks for your help.