LiveKit Community

Have you configured turn server? Sometime it helps with web.

<@U02KJGV339S> it sounds that it can connect to the websocket but is having issues with establishing peerconnection. As Jibon mentioned, it's possible that there are NAT/firewalls on the client side that's preventing access.

When you say 50% of the times, is that for your users? or is that for you during testing? If it's a firewall issue, it would likely be that certain users would consistently not be able to use it.

it’s for me during testing, same networks and it works some times around 50%, also we have tried with turn servers and without, what I also noted is that when our LiveKit server is setup from source it’s reliable, I’m only noting this issues when using the docker image for the server

<@U02KJGV339S> Most probably you aren't using host network for your livekit docker configuration. You can try docker compose file with host network. Quick example: <https://github.com/mynaparrot/plugNmeet-install/blob/a23fae9178f666af87731662241ad67cd8d6c573/install-files/docker-compose.yaml#L28>

LiveKit itself does not control the layout. There are some example layouts, but the expectation is that you will be writing your own interface. Because of this, you have full control over it - but it does require development effort unless the basic examples work for your needs.

I get it.  but in one of the demos I saw that they had a button in the upper right corner that made a switch between two different layouts.  But I don't remember the exact page where I saw it.  that's why I asked the question.  in case there was a function that controlled the default layout.
But, thanks for answering 

As <@U02C10ZEP8R> mentioned with LiveKit you can get full WebRTC solution with excellent client SDK. Now you can give effort to setup your own interface. Livekit will take care audio/video broadcasting, your interface will be responsible to display.

<@U035SJ598AD> I think you are referring to the <https://github.com/livekit/livekit-react/blob/master/src/components/StageView.tsx#L35|two default layouts> we are providing via the React SDK.

As both bekit and Jibon mentioned, these are there primarily as examples of what you could build with LiveKit. You are more than welcome to use them in your application.

If you are using the default `LiveKitRoom` component, you can provide a Context that set `stageLayout` param to the desired one like <https://github.com/livekit/livekit-react/blob/master/example/src/RoomPage.tsx#L56|here>

Yes, thank, <@U01KZ61GV5Z>. thank you very much it's just what I was looking for

Screenshot 2022-04-24 at 12.37.17 PM.png

Unfortunately, that's not currently possible. However, there's now a `sortby` option that can be set for the nodes that can help spread load out early. You could have it spread by number of rooms, used bandwidth, cpu load, etc.

There could still be a case like you described, but it should help some (and has in my cluster).

There's some migration code that has gone in recently. I'm hoping that gets exposed on the OSS offering as well so we can have some logic to balance nodes after room creation. Even if a room has to live on a single node, being able to easily migrate them based on conditions would be a huge benefit.

hi <@U03DE2H858Q>,
thanks for the report, turns out we were missing a "type": "module" setting in the package.json to hint to vitejs' rollup setup that livekit-client is not a commonjs module, but rather an esmodule.
Fix is in main already for you to try by referencing the repo directly, but will also release a patch on npm for it sometime today!

v0.18.3 is released, confirmed svelte-kit build working :slightly_smiling_face:

Wow, that was fast! Thank you so much :tada:

Tracks are for individual video/audio tracks, while a participant contains 0-many tracks. Tracks can't exist without a participant, but a participant can exist without any tracks (e.g. a passive participant who isn't publishing any audio/video).

it'll depend on the usecase which one is appropriate. You'd want to listen for the participant pair for dealing with participant views (though the participants given from the `useRoom()`  state in the react sdk might be more appropriate for this), and tracks for video size etc.

wow, this is AWESOME to see!

You should be able to make it work within Docker too without port forwarding. We've addressed it in <https://github.com/livekit/livekit-server/pull/624|this PR>. Give it a try and see if that works for you.

We are about to cut a new release that includes it.

Thanks David,
I was able to get it to work locally on the network and between local VLANs.  I was not able to get it to run through NAT.  Tried running locally natively and within a container.

Assuming the docker container is running on a 192.168.1.5 host, which has a public address of 1.2.3.4. would this be the subset of the config for that?

```rtc:
  use_external_ip: false
  stun_servers:
    - 192.168.1.5
    - 1.2.3.4```

we don't have an out of the box solution for this at the moment, but it can be done by creating the LocalVideoTrack with your own video capturer

<https://docs.livekit.io/client-sdk-android/livekit-android-sdk/io.livekit.android.room.participant/-local-participant/create-video-track.html>

You can see how to create a Camera2Capturer <https://github.com/livekit/client-sdk-android/blob/1a053234f089e16b8f17e0e1c1d3b6c8e966bc0b/livekit-android-sdk/src/main/java/io/livekit/android/room/track/LocalVideoTrack.kt#L191|here>

Thanks. I will take a look into this. Out of the box solution not expected, and this is a good starting point. Much appreciated

ah, you will probably need to build the LocalVideoTrack manually, as I think we overwrite the CapturerObserver (which is what you'll use to get the frames).

there's an example of another user building it manually here:
<https://livekit-users.slack.com/archives/C01KVTJH6BX/p1644455437430419?thread_ts=1644384910.562039&amp;cid=C01KVTJH6BX>

Hi Lauren, is it possible that you are running your local client on a http (i.e. not https) host? Some, if not all, browsers prevent certain types of connections from non-encrypted pages.

Ah okay, I am using http on 127.0.0.1
I’ll have a try with this tonight. 
Thanks! 

It still didn't work using localhost.
But, I tried building and running the livekit server instead of using docker and that worked. Which is a bit weird.
Glad I can get started using this :smile:

I think you might be looking for the TrackMuted/TrackUnmuted events fired from the participant/room?

<@U01NZKTNE1H> That saved the day, THANK YOU!

Ahmed, if you are using the React SDK, you shouldn't need to manage state by yourself. the provided hooks should handle it for you!

i.e. for your component that renders any participant data, you could use <https://github.com/livekit/livekit-react/blob/a7cb19618e3725d0ad6e952abfca368b60035ade/src/useParticipant.ts#L11|useParticipant> hook. the variables are updated automatically when the underlying state changes

for camera publication state, you could do
```const { cameraPublication } = useParticipant(participant);

if (!cameraPublication?.isMuted) {
  // not muted
} else {
  // muted
}```

Hi David, thanks so much, I need to detect camera and mic status change on the room level as i maintain a list of “active” users with camera &amp; mic and render a specific component (viewer) for them only, if someone turns camera off, they stay in the room but no component will be rendered for them

Heya, yeah I actually authored that piece. I created a managed cert ingress independently and then named it in the chart iirc. I added these instructions from gcp: <https://github.com/livekit/livekit-helm/blob/master/server-sample.yaml#L45-L46>
Apologies they are kinda hard to find

Great thanks, I'll try it out and report back

Just to clarify, am I responsible for bringing my own ingress in this scenario, or does the helm chart handle that for me

it seems from reviewing the code that it's supposed to be handled for me but it isn't.  Not yet anyway

yeah correct, you have to create the managed ingress separately. the lk helm chart doesn't create it for you

k.  I am following steps 1-6 from that document you sent and then will try the helm chart again.

Let me know if that works. I've got to run through the same setup today on my project and can troubleshoot if needed

So I think it worked except I'm still having issues connecting.  I get the error "server was not reachable" so I suspect I've got something wrong with the firewall

OK, I finally got everything working, I think.  One thing, the helm chart created the service as ClusterIP, but GKE ingress required NodePort.  Are you aware of this or did I configure something wrong?

FWIW, Same ^ (as last message in this thread)

can you try with the latest 0.18.3 ? we had a change in the way we bundle the library and reverted some stuff in 0.18.3 in order to support older devices

<@U02EU2ZPTQU> I tried both and both not compiling to backward compatible code, only 0.17.5 working well.

I using webpack and ts-loader to pack my code, probably I need some additional configuration there now? going to research

for additional configurations, does your setup run babel at the moment?

~also setting the target of your ts config to `ES5` could solve your problem~
(realising that the ts target would most likely not make a difference as the code is already compiled to js)

<@U02EU2ZPTQU> not using babel at the moment, should I add it? never tried it before :slightly_smiling_face:

one way to ensure backwards compatibility would be using babel, yes. using their preset `preset-env` <https://babeljs.io/docs/en/babel-preset-env> allows you to specify specific targets that you'd want to support.

But anyways I'll raise your issue internally and see how far back we should go in supporting targets out of the box.

Hi all, i've managed to compile and run livekit server on raspberry pi, but i have small problem, After starting docker container i'm able to connect to livekit server, but if somoene will decide to disconnect i'm getting following error:

```2022-04-26T22:59:42.743Z	DEBUG	livekit	rtc/room.go:200	participant state changed	{"room": "xj3p1ymjsoot8q6n1iheihyz6d56w6tu", "roomID": "RM_aHVRrPfASzYS", "state": "DISCONNECTED", "participant": "Gamemaster", "pID": "PA_F57RMSmot57H", "oldState": "ACTIVE"}
panic: unaligned 64-bit atomic operation
goroutine 253 [running]:
runtime/internal/atomic.panicUnaligned()
	/usr/local/go/src/runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Store64(0x25d70bc, 0x6268781f)
	/usr/local/go/src/runtime/internal/atomic/atomic_arm.s:301 +0x14
<http://go.uber.org/atomic.(*Int64).Store(...)|go.uber.org/atomic.(*Int64).Store(...)>
	/go/pkg/mod/go.uber.org/atomic@v1.9.0/int64.go:75
<http://github.com/livekit/livekit-server/pkg/rtc.(*Room).RemoveParticipant|github.com/livekit/livekit-server/pkg/rtc.(*Room).RemoveParticipant>(0x25d6f00, {0x242c800, 0xa})
	/workspace/pkg/rtc/room.go:340 +0x348
created by <http://github.com/livekit/livekit-server/pkg/rtc.(*Room).Join.func1|github.com/livekit/livekit-server/pkg/rtc.(*Room).Join.func1>
	/workspace/pkg/rtc/room.go:221 +0x334```

<@U03D29B0PNW> we haven't gotten around to test this on arm7 yet. Though there's really nothing preventing it from working on that platform.

I think it's mostly due to some use of atomics in the code base. If you are interested in fixing these little things, I'd be happy to support that effort!

Hi, thanks for the feedback, at the moment its not something i would be working on, especially that i'm not familiar with GO. However if you would be planning to extend support for arm7 it would be great, as so far livekit is working nicely on raspberry pi (except for this disconnect issue). For no i have it resolved by running docker with  --restart unless-stopped flag, and seems to be sufficient.

hi!
are you trying to unmute a remote track or your local track?

<@U03C8KQDJMA> this is expected (and is a privacy feature). To enable unmuting of participants from the server side, you'd want to enable <https://github.com/livekit/livekit-server/blob/master/config-sample.yaml#L116|enable_remote_unmute>

Screen Recording 2022-04-27 at 5.09.10 PM.mov

can you share the command you are using to launch the docker container?

Here you are: docker run --rm \
  -p 7880:7880 \
  -p 7881:7881 \
  -p 7882:7882/udp \
  -v $PWD/livekit.yaml:/livekit.yaml \
  livekit/livekit-server \
  --config /livekit.yaml \
  --node-ip=127.0.0.1

can you try setting `--node-ip` to the machine's IP address instead of loopback?

Screen Shot 2022-04-27 at 7.44.22 PM.png

I just tried it like this, however Iam experiencing the same issue:
docker run --rm \
  -p 7880:7880 \
  -p 7881:7881 \
  -p 7882:7882/udp \
  -v $PWD/livekit.yaml:/livekit.yaml \
  livekit/livekit-server \
  --config /livekit.yaml \
  --node-ip=192.168.0.95

```Here is my log:
2022-04-27T17:46:41.331Z	INFO	livekit	logger/logger.go:26	using single-node routing
2022-04-27T17:46:41.399Z	INFO	livekit	logger/logger.go:30	UDP receive buffer is too small for a production set-up	{"current": 425984, "suggested": 5000000}
2022-04-27T17:46:41.401Z	INFO	livekit	logger/logger.go:26	starting LiveKit server	{"addr": ":7880", "nodeID": "ND_fSEES70M", "nodeIP": "192.168.0.95", "version": "0.15.6", "rtc.portTCP": 7881, "rtc.portUDP": 7882}
2022-04-27T17:46:42.554Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_Muht7vwBrfLQ", "pID": "PA_nYaoyvoW7W8d", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T17:46:42.555Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_Muht7vwBrfLQ"}
2022-04-27T17:46:52.632Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}
2022-04-27T17:47:41.356Z	INFO	livekit	rtc/room.go:488	closing room	{"room": "stark-tower", "roomID": "RM_Muht7vwBrfLQ"}
2022-04-27T17:47:41.356Z	INFO	livekit	logger/logger.go:26	deleting room state	{"room": "stark-tower"}
2022-04-27T17:47:41.357Z	INFO	livekit	logger/logger.go:26	room closed
2022-04-27T17:48:24.994Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_RfnWLgspbTN2", "pID": "PA_hFKEZrrEUYNU", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T17:48:24.995Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_RfnWLgspbTN2"}
2022-04-27T17:48:35.061Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}
2022-04-27T17:49:11.294Z	INFO	livekit	rtc/room.go:488	closing room	{"room": "stark-tower", "roomID": "RM_RfnWLgspbTN2"}
2022-04-27T17:49:11.294Z	INFO	livekit	logger/logger.go:26	deleting room state	{"room": "stark-tower"}
2022-04-27T17:49:11.295Z	INFO	livekit	logger/logger.go:26	room closed
2022-04-27T18:07:47.985Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_bUkXGWjT7LPv", "pID": "PA_vrgF6HeK34L5", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T18:07:47.986Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_bUkXGWjT7LPv"}
2022-04-27T18:07:58.052Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}
2022-04-27T18:08:40.425Z	INFO	livekit	rtc/room.go:488	closing room	{"room": "stark-tower", "roomID": "RM_bUkXGWjT7LPv"}
2022-04-27T18:08:40.426Z	INFO	livekit	logger/logger.go:26	deleting room state	{"room": "stark-tower"}
2022-04-27T18:08:40.426Z	INFO	livekit	logger/logger.go:26	room closed
2022-04-27T18:10:39.658Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_pefWX3tU8dXm", "pID": "PA_PzmaUTijrnb2", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T18:10:39.659Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_pefWX3tU8dXm"}
2022-04-27T18:10:49.716Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}
2022-04-27T18:11:10.316Z	INFO	livekit	rtc/room.go:488	closing room	{"room": "stark-tower", "roomID": "RM_pefWX3tU8dXm"}
2022-04-27T18:11:10.316Z	INFO	livekit	logger/logger.go:26	deleting room state	{"room": "stark-tower"}
2022-04-27T18:11:10.317Z	INFO	livekit	logger/logger.go:26	room closed
2022-04-27T18:13:08.476Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_L2T8q9qtgaX4", "pID": "PA_3hrKMKGHCkhu", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T18:13:08.477Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_L2T8q9qtgaX4"}
2022-04-27T18:13:18.560Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}
2022-04-27T18:13:40.204Z	INFO	livekit	rtc/room.go:488	closing room	{"room": "stark-tower", "roomID": "RM_L2T8q9qtgaX4"}
2022-04-27T18:13:40.204Z	INFO	livekit	logger/logger.go:26	deleting room state	{"room": "stark-tower"}
2022-04-27T18:13:40.204Z	INFO	livekit	logger/logger.go:26	room closed
2022-04-27T18:13:45.137Z	INFO	livekit	rtc/room.go:227	new participant joined	{"room": "stark-tower", "roomID": "RM_ntNi2aAozMVX", "pID": "PA_5abZHrpcpNge", "participant": "tony_stark", "protocol": 7, "options": {"AutoSubscribe":true}}
2022-04-27T18:13:45.138Z	INFO	livekit	service/rtcservice.go:199	new client WS connected	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark", "roomID": "RM_ntNi2aAozMVX"}
2022-04-27T18:13:55.228Z	INFO	livekit	service/rtcservice.go:180	server closing WS connection	{"room": "stark-tower", "participant": "tony_stark", "connID": "tony_stark"}```

this is showing it's not able to establish websocket connection for some reasons.. will take a look at why that's not working with the flutter app.

<@U03CQQY5154> how does this work for you?
```docker run --rm \
  -p 7880:7880 \
  -p 7881:7881 \
  -p 7882:7882/udp \
  -v $PWD/livekit.yaml:/livekit.yaml \
  livekit/livekit-server:vfix-node-ip-SNAPSHOT \
  --config /livekit.yaml \
  --node-ip=&lt;your-machine-ip&gt;```

thank you for confirming! I'll cut a new release with it

screenshot.png

what is displayed is the actual key.. i.e.
`APIbRwMKqhD48uJ`

Ok I tried "APIbRwMKqhD48uJ" and "bRwMKqhD48uJ," got 401:

```SignalClient.ts:152 WebSocket connection to '<ws://localhost:7880/rtc?access_token=APIbRwMKqhD48uJ&amp;sdk=js&amp;version=0.17.1&amp;protocol=6>' failed: 
(anonymous) @ SignalClient.ts:152
connect @ SignalClient.ts:149
(anonymous) @ SignalClient.ts:120
(anonymous) @ RequestQueue.ts:3
push.../node_modules/livekit-client/dist/api/SignalClient.js.__awaiter @ RequestQueue.ts:3
join @ SignalClient.ts:112
(anonymous) @ RTCEngine.ts:91
(anonymous) @ PCTransport.ts:5
push.../node_modules/livekit-client/dist/room/RTCEngine.js.__awaiter @ PCTransport.ts:5
join @ RTCEngine.ts:86
(anonymous) @ Room.ts:198
(anonymous) @ RTCEngine.ts:617
push.../node_modules/livekit-client/dist/room/Room.js.__awaiter @ RTCEngine.ts:617
Room.connect @ Room.ts:179
(anonymous) @ useRoom.ts:38
_catch @ helpers.mjs:565
(anonymous) @ useRoom.ts:38
(anonymous) @ LiveKitRoom.tsx:38
invokePassiveEffectCreate @ react-dom.development.js:23487
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
flushPassiveEffectsImpl @ react-dom.development.js:23574
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushPassiveEffects @ react-dom.development.js:23447
(anonymous) @ react-dom.development.js:23324
workLoop @ scheduler.development.js:417
flushWork @ scheduler.development.js:390
performWorkUntilDeadline @ scheduler.development.js:157
SignalClient.ts:158          GET <http://localhost:7880/rtc/validate?access_token=APIbRwMKqhD48uJ&amp;sdk=js&amp;version=0.17.1&amp;protocol=6> 401 (Unauthorized)
(anonymous) @ SignalClient.ts:158
(anonymous) @ RequestQueue.ts:3
push.../node_modules/livekit-client/dist/api/SignalClient.js.__awaiter @ RequestQueue.ts:3
ws.onerror @ SignalClient.ts:155
error (async)
(anonymous) @ SignalClient.ts:155
connect @ SignalClient.ts:149
(anonymous) @ SignalClient.ts:120
(anonymous) @ RequestQueue.ts:3
push.../node_modules/livekit-client/dist/api/SignalClient.js.__awaiter @ RequestQueue.ts:3
join @ SignalClient.ts:112
(anonymous) @ RTCEngine.ts:91
(anonymous) @ PCTransport.ts:5
push.../node_modules/livekit-client/dist/room/RTCEngine.js.__awaiter @ PCTransport.ts:5
join @ RTCEngine.ts:86
(anonymous) @ Room.ts:198
(anonymous) @ RTCEngine.ts:617
push.../node_modules/livekit-client/dist/room/Room.js.__awaiter @ RTCEngine.ts:617
Room.connect @ Room.ts:179
(anonymous) @ useRoom.ts:38
_catch @ helpers.mjs:565
(anonymous) @ useRoom.ts:38
(anonymous) @ LiveKitRoom.tsx:38
invokePassiveEffectCreate @ react-dom.development.js:23487
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
flushPassiveEffectsImpl @ react-dom.development.js:23574
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushPassiveEffects @ react-dom.development.js:23447
(anonymous) @ react-dom.development.js:23324
workLoop @ scheduler.development.js:417
flushWork @ scheduler.development.js:390
performWorkUntilDeadline @ scheduler.development.js:157
SignalClient.ts:152 WebSocket connection to '<ws://localhost:7880/rtc?access_token=bRwMKqhD48uJ&amp;sdk=js&amp;version=0.17.1&amp;protocol=6>' failed: 
(anonymous) @ SignalClient.ts:152
connect @ SignalClient.ts:149
(anonymous) @ SignalClient.ts:120
(anonymous) @ RequestQueue.ts:3
push.../node_modules/livekit-client/dist/api/SignalClient.js.__awaiter @ RequestQueue.ts:3
join @ SignalClient.ts:112
(anonymous) @ RTCEngine.ts:91
(anonymous) @ PCTransport.ts:5
push.../node_modules/livekit-client/dist/room/RTCEngine.js.__awaiter @ PCTransport.ts:5
join @ RTCEngine.ts:86
(anonymous) @ Room.ts:198
(anonymous) @ RTCEngine.ts:617
push.../node_modules/livekit-client/dist/room/Room.js.__awaiter @ RTCEngine.ts:617
Room.connect @ Room.ts:179
(anonymous) @ useRoom.ts:38
_catch @ helpers.mjs:565
(anonymous) @ useRoom.ts:38
(anonymous) @ LiveKitRoom.tsx:38
invokePassiveEffectCreate @ react-dom.development.js:23487
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
flushPassiveEffectsImpl @ react-dom.development.js:23574
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushPassiveEffects @ react-dom.development.js:23447
(anonymous) @ react-dom.development.js:23324
workLoop @ scheduler.development.js:417
flushWork @ scheduler.development.js:390
performWorkUntilDeadline @ scheduler.development.js:157
SignalClient.ts:158          GET <http://localhost:7880/rtc/validate?access_token=bRwMKqhD48uJ&amp;sdk=js&amp;version=0.17.1&amp;protocol=6> 401 (Unauthorized)```

you are using it as an access token.. that's incorrect. please refer to <https://docs.livekit.io/guides/access-tokens|access token docs>

have you checked out the <https://docs.livekit.io/deploy/vm#troubleshooting|troubleshooting section> from our docs?

Oracle cloud enables its instance-specific firewall, so you'll need to disable it

Hi. I have, yes. Oracle Cloud firewal is iptables based, not firewall-cmd as per your docs. So i've tried:

```sudo iptables -I INPUT 6 -m state --state NEW -p tcp --match multiport --dports 80,443,7881 -j ACCEPT

sudo iptables -I INPUT 6 -m state --state NEW -p udp --match multiport --dports 443,50000:60000 -j ACCEPT```
as well as

```sudo iptables -F```
to flush everything just to be sure

but i don't think that's the issue, since the connection tester responded differently when i had those ports closed.

This error i'm getting is "Internal error", which to me seems to be occuring AFTER a connection has been made, and is something happening within the livekit-docker service itself. perhaps i'm wrong.

I don't know how to even begin debugging this, which is why i'm asking here

ah interesting. that's good to know re: iptables. FWIW I have used firewall-cmd successfully on Oracle VMs.

Regarding the internal error, what do you see in the server logs? i.e. with `docker-compose logs`

logs.txt

here it is, sorry for the delay i had to figure out scp to get it from the server

notably, i see the error
```v2@v2.0.8/server.go:184	error when handling datagram: failed to create stun message from packet: BadFormat for message/cookie: 1d0b82e6 is invalid magic cookie (should be 2112a442)```
repeated over and over, and no trace of any
```"logger":"tls.obtain","msg":"certificate obtained successfully"```
which the docs mention should appear

I think you have already gotten past the certificate generation, you can verify by going to https://&lt;yoururl&gt;

it does, yes :slightly_smiling_face: That's a smaller rock off my chest, but yea.. the error...

it seems that somehow you've gotten a malformed UDP packet...

the client sends a UDP packet to the server, but somehow that packet isn't what the server is expecting

actually can you send logs while the client is making a request? I'm not seeing anything in the logs that indicate that it has received it

that would explain why i had no clue (and still don't) regarding this. all i know is, i've deployed the service precisely as per the docs, nothing more nothing less, and put in wss://&lt;myurl&gt; and the sample token received from when i created the server into the connection tester

i'll try that now. will make the client request a bunch of times and come back with a new set of logs

is there any way to get the logs dynamically as they come in?

this is the new set of logs made just after running the client a couple of times just now. maybe the more recent timestamps will help?

image.png

shameless bump :smile:

Please let me know if I should file an issue on github as well for this, and/or if you have any more insights into this...

Hey <@U01KZ61GV5Z> , sorry to bother you with this, i don't wanna come off as overbearing :smile: please do let me know how we should proceed with this

The problem was due to Firefox. Edge and Chrome work just fine.

Damn...

specifically the Ublock Origin adblocker plugin

sorry, I missed this thread until now.. but I'm glad you found the root cause.. I'll make a mental note about this. This plugin blocks WebRTC connections..

Glad to have reported it :D thx for everything &amp;&amp; keep up the good work :+1:

<@U01KZ61GV5Z>, Hi! Could you please give me a few words about your plans regarding nodes downscaling and rooms migrations? It’s important for my own plan too.

Ivan, downscaling is quite straight forward. When LiveKit server receives TERM, it puts itself into Drain mode. That is: it will not accept new rooms to be allocated to it, but will allow current rooms to finish.
Room migrations are possible, but would trigger a reconnect from the clients. It should be handled automatically though.

Wow, Drain mode is clever! Thanks! Have a good day)

<@U03C8KQDJMA> yes! you can use <https://docs.livekit.io/client-sdk-js/classes/Participant.html#audioLevel|Participant.audioLevel>

Thanks a lot.
Too bad it's not implemented in the react hook yet.

it should just work within the hook.. you still have the participant object

and whenever the volume changes, the hook will cause state to change

the data will already include info about participant who sent it (i.e. the `DataReceived` events emitted will include references to the participant)

if you want to send any other custom data, that's up to you to determine how to format the data (could just go with JSON for simplicity)

Oh, then how can i send data in json format through livekit server?

you can just send it through the `publishData` method.

String natively has a `getBytes` method to get a byte array

I just did it successfully, thanx again <@U01NZKTNE1H>

I assume you mean OBS RTMP -&gt; LiveKit? If so that's in progress!

Thanks <@U01KZ61GV5Z>. That's what I was referring to yes.

I get error could not connect after timeout when I try to use livekit

<http://example.livekit.com|example.livekit.com> seems to be working properly

but the react client goes derp for some reason

gives me an "error could not connect after timeout"

ok, this may just be because my code is sloppy

because a self-hosted <http://example.livekit.com|example.livekit.com> works