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

trusted websocket #138

Open
22350 opened this issue Jul 23, 2021 · 3 comments
Open

trusted websocket #138

22350 opened this issue Jul 23, 2021 · 3 comments

Comments

@22350
Copy link

22350 commented Jul 23, 2021

instances keep saying that i need to trust the web-socket. I have tried all sorts of things, but no luck

@sabogalc
Copy link

sabogalc commented Aug 8, 2021

Are you using https for SMServer? It should be as easy as going to https://your.ip:websocket.port.number and allowing your device to connect to that address, then going back to the IP web address that has your main port attached to it.

@itsjunetime
Copy link
Owner

Could you also go into more detail about exactly what you try to do to trust the websocket, what client you're using, and what your settings are on the host with regard to SSL, authentication, and the port numbers of both your websocket and main server?

@ayueyue321
Copy link

I don't know how to solve the same problem

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

4 participants