https://livekit.io logo
Join Slack
Powered by
How can i change my project URL?
# ask-ai
r
How can i change my project URL?
t
Thanks for reaching out, Shreyansh. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
I'd be happy to help you change your project URL in LiveKit! Here’s a simple guide to walk you through the process: • Using the LiveKit CLI: a. First, remove the existing project by running: 
lk project remove PROJECT_NAME
b. Then, add the project again with your updated URL: 
lk project add PROJECT_NAME --url <wss://new-subdomain.livekit.cloud> --api-key YOUR_API_KEY --api-secret YOUR_API_SECRET [--default]
c. Finally, you can list your projects to make sure everything looks good: 
lk project list
• For Environment Variables: If your app uses a 
.env
file, just update the 
LIVEKIT_URL
value there and restart your application to apply the changes. • For LiveKit Cloud: Just a heads-up, the project URL is linked to the subdomain and can’t be changed after creation. So, you’ll need to create a new project with the subdomain you want and then update your application accordingly. Please feel free to reach out if you have any questions or need a hand with any of these steps—I’m here to help! Sources: web/.env.sample | .env.example | .env.example | examples/receive-audio/.env.example | LiveKit CLI project management | LiveKit Docs
r
There is no stream running with ingress right now, still why then it says that Concurrent ingress request is 107? Am I missing something here?
t
Hi there! I understand that seeing a high "Concurrent Ingress requests" count on your dashboard can be a bit confusing, so let’s explore some common reasons together: • Ingress State Persistence: Sometimes, streams that have just ended might still appear as active because the cleanup process is still wrapping up. • Delayed Status Updates: Your ingress endpoints might stay in a buffering or publishing state if they’re still connected or reconnecting intermittently. • Pending or Stale Requests: Brief interruptions, like encoder restarts, can temporarily show as active connections until they fully disconnect. • Monitoring Artifacts: The metrics you see might reflect recent activity rather than the exact real-time status. To help you dig a little deeper, here are some steps you can try: • Use the 
ListIngress
API or your dashboard to check the current state of your ingress endpoints. • Look out for any inactive ingresses that might need to be deleted or disabled. • Try the 
ListActiveIngressRequest
API to get a real-time snapshot of active ingress sessions. If you’d like, I’m here to guide you through any of these steps—just let me know! Sources: Webhooks | LiveKit Docs | protobufs/livekit_ingress.proto | pkg/stats/monitor.go
Open in Slack
PreviousNext
Powered by