Why my agent is dying? ``` 07:26:43.127 DEBUG l...
# ask-ai
a
Why my agent is dying?
Copy code
07:26:43.127 DEBUG  livekit.…echStream Starting audio         
                                           processing             
                                           {"session_id": 
137662762567184, "chunk_size": 800, "pid": 2962264, "job_id": 
"AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
                 INFO   livekit.…echStream Starting message       
                                           processing             
                                           {"session_id": 
137662762567184, "ws_closed": false, "pid": 2962264, "job_id": 
"AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
error: failed to fetch server settings: http status: 404
    07:26:43.290 ERROR  livekit            livekit_ffi::server:…  
                                           - audio filter cannot  
                                           be enabled: LiveKit    
                                           Cloud is required      
                                  {"pid": 2962264, "job_id": 
"AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
    07:26:43.297 DEBUG  livekit.agents     using audio io:        
                                           `RoomIO` ->            
                                           `AgentSession` ->      
                                           `TranscriptSynchroni…  
                                           -> `RoomIO`            
                                         {"pid": 2962264, 
"job_id": "AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
                 DEBUG  livekit.agents     using transcript io:   
                                           `AgentSession` ->      
                                           `TranscriptSynchroni…  
                                           -> `RoomIO`            
                                         {"pid": 2962264, 
"job_id": "AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
    07:27:16.800 DEBUG  livekit.agents     input stream detached  
                                         {"participant": 
"user-4abee073", "source": "SOURCE_UNKNOWN", "accepted_sources": 
["SOURCE_MICROPHONE"], "pid": 2962264, "job_id": 
"AJ_8pBKPhVrNeMQ", "room_id": "RM_sYjwWnXGKjfq"}
Transcript for room-4abee073 saved to artifacts/transcripts/transcript_room-4abee073_20251223_072718.json
    07:27:18.803 DEBUG  livekit.…echStream Starting stream        
                                           cleanup                
                                           {"session_id": 
137662762567184, "pid": 2962264, "job_id": "AJ_8pBKPhVrNeMQ", 
"room_id": "RM_sYjwWnXGKjfq"}
t
Thanks for reaching out, Aditya. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I looked at the logs you pasted. Two things are causing the agent to stop: 1) Failed to fetch server settings (HTTP 404) • The agent tried to contact your LiveKit server to get settings and received a 404, so it couldn’t load required configuration. Check your
LIVEKIT_URL
(ensure it points to a valid LiveKit endpoint) and confirm the server endpoint and routing are correct. 2) Cloud-only audio filter attempted on a non-Cloud deployment • The agent tried to enable an enhanced audio filter (BVC/noise cancellation) which requires LiveKit Cloud. That feature cannot be enabled on self-hosted instances and will fail. Remove or disable Cloud-only filters in your agent config, or run on LiveKit Cloud if you need BVC. Quick actions to try • Verify
LIVEKIT_URL
,
LIVEKIT_API_KEY
, and
LIVEKIT_API_SECRET
(redact secrets when sharing). • If self-hosted, disable BVC / cloud noise-cancellation in your audio input options. • Re-run with full debug logs and confirm the agent can reach the server and the room exists. If you want, share the agent startup snippet (with secrets redacted) and the
LIVEKIT_URL
format you’re using and I’ll point out exactly what to change. Sources: Simple Call Answering Agent | LiveKit docs | Generating tokens | LiveKit docs | Configuring firewalls | LiveKit docs | Enhanced noise cancellation | LiveKit docs | Noise & echo cancellation | LiveKit docs
a
error: failed to fetch server settings: http status: 404 073407.424 ERROR livekit livekit_ffi:server… - audio filter cannot be enabled: LiveKit Cloud is required Why I am getting this error?
t
You're seeing two related issues. Short answer: the agent can't reach valid server settings (404) and it's trying to enable a Cloud-only audio filter. Why each error appears • "failed to fetch server settings: http status: 404" The agent requested configuration from your LiveKit server but got a 404 Not Found. That means the URL or endpoint it called is incorrect or the server routing/endpoint isn’t present (room or API path not found). • "audio filter cannot be enabled: LiveKit Cloud is required" Your code is attempting to enable an enhanced audio filter (e.g., BVC/noise cancellation) that is only available on LiveKit Cloud. That feature is unavailable on self-hosted servers and the SDK reports this error. What to do next • Verify
LIVEKIT_URL
is correct and reachable (use the proper wss/http scheme for your deployment). • Confirm the room or API endpoint exists and the server is up. • If self-hosted, remove or disable Cloud-only audio filters (disable BVC/noise_cancellation). Use basic WebRTC suppression or
AudioCaptureOptions
instead. • If you require BVC, run the agent against LiveKit Cloud. If you want, paste the agent startup snippet and the
LIVEKIT_URL
format (redact secrets) and I’ll point out the exact values to change.
a
it is working, the worker is getting registered
Copy code
2025-12-23T07:35:53.101Z        INFO    livekit.agents  service/agentservice.go:298     worker registered       {"namespace": "", "jobType": "JT_ROOM", "agentName": "", "workerID": "AW_7U3xE59mZeiN"}