I created this agent with EU Central region selected, but logs show it registers in EU West B (Marseille). The agent then fails with failed to retrieve region info when calling Room.connect(). The /settings/regions endpoint is reachable from a browser but not from within the container. SDK version: @livekit*/agents@1.0.35.*
My voice agent was deployed to EU Central region but registers on LiveKit side as EU West B region so the room can’t connect. It’s not something I can fix on my side. Can you help?
I took a look at the project associated with your email and I can only see one agent, CA_xxxxxxJjJg54 but that is hosted in the us-east region.
Regardless, assuming I just can’t find the relevant agent, I think you are conflating agent hosting (EU Central) with region pinning (EU West B). I wrote a field guide the other day, Checklist for Regional Deployments | LiveKit, please take a look through that
You guys take too long to reply so I made another plan and deleted the agent and switched over to US East although it’s a big latency issue for me it’s nothing I can fix. You guys must have a look into the issue I had because others will have the same issue as me in the future.
Also make a dedicated support contact page or something because we can’t wait a day or 2 for feedback from support.