This message was deleted.
# helpdesks
steep-balloon-41261
10/30/2023, 2:27 PMThis message was deleted.
a
adorable-ram-93016
10/30/2023, 2:27 PMnot sure how i can get this working since my .env keys and everything are all correct, and there are no other errors in the project
just this internal server error
i am using liveKit cloud
a
acoustic-engineer-41666
10/30/2023, 2:28 PMthe internal server error is our fault, we’ll look into it today
acoustic-engineer-41666
10/30/2023, 2:30 PMas for the usage limits, can you dm me your ws url so I can look at your project?
a
adorable-ram-93016
10/30/2023, 2:35 PMyes it's wss://loop-claw-bqzheizc.livekit.cloud
and for what its worth, my dashboard is showing almost zero usage:
đź‘€ 1
adorable-ram-93016
10/30/2023, 5:06 PMi noticed in the repo, in the create and delete ingress .tsx files there doesnt seem to be any visible buttons to delete endpoints that have been created.
could that be the problem? maybe there are just a bunch of endpoints being created and not being closed?
adorable-ram-93016
10/30/2023, 5:06 PMshould there be a button on the page to enable this?
adorable-ram-93016
10/31/2023, 8:45 PMany chance you were able to resolve this? i can't seem to stream on any projects, i tried deleting them all and starting new ones
a
acoustic-engineer-41666
11/01/2023, 4:27 AMhey so, yes there’s two issues here:
1. the 500s should be resolved now, as of our deploy today. please let us know if you continue seeing these.
2. Ingresses can be a little unintuitive in that once you create them they stick around and can be re-used. (This is so that you can set up OBS Studio once and not have to reconfigure it for every stream.)
We disabled it in the example app, but you can show the “delete ingresses” button (whose code you screenshotted) by setting the env var
NEXT_PUBLIC_ENABLE_DANGER_ZONE=1a
adorable-ram-93016
11/01/2023, 4:37 PMawesome thank you!