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

An exception occurred while using the go SDK "ConnectToRoom" API #58

Open
dht-hedaihua opened this issue May 3, 2022 · 1 comment
Open

Comments

@dht-hedaihua
Copy link

dht-hedaihua commented May 3, 2022

Describe the bug
When I use the connecttoroom view of the example method of livekit go SDK to connect to a room I have entered through the web, the server can monitor my connection, but soon it automatically turns off the connection. The specific process is as follows:
Premise:
I have successfully started the livekit service in the docker of my Mac. As follows:
image
Then I successfully connected to the livekit service I had started locally through the livekit client JS end example. As follows:

image

image

Now:
I call the sample code in livekit go SDK in the local go project. I try to connect to the room just created on the web side. The code is as follows:

image

After execution, the output information of the server and connection end is as follows:
Print information at the service startup terminal:
image

The upper part shows that the client connection is automatically executed in a very short time from closing the connection. I didn't do anything.

The log information printed on the connection console is:
image

Additional Comments:
I changed the protocol of the host in the connection section parameters to WSS, HTTPS and HTTP respectively, and the connection address to localhost and my local IP address respectively. The server will respond only when it is WS: / / localhost: 7880. In other cases, the connection timeout or TLS handshake is reported.

Server

  • Version: [0.15.7]
  • Environment: [local docker MacOS]

Client

@davidzhao
Copy link
Member

@HDHChris it might be related to this issue. In any case, since this is connectivity of the Go SDK, moving it to that repo.

@davidzhao davidzhao transferred this issue from livekit/livekit May 3, 2022
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

2 participants