https://livekit.io logo
Join Slack
Powered by
error: failed to fetch server settings: http statu...
# ask-ai
c
error: failed to fetch server settings: http status: 404 2025-12-28 135611,549 - INFO - Yeni session başlatıldı: 09fe427f-752f-4213-ae21-717b6e087426 2025-12-28 135611,549 - INFO - Yeni session başlatıldı: 09fe427f-752f-4213-ae21-717b6e087426 2025-12-28 135611,551 - ERROR - livekit_ffi:serverroom149livekit ffiserver:room - audio filter cannot be enabled: LiveKit Cloud is required 135611.549 INFO __mp_main__ Yeni session başlatıldı: 09fe427f-752f-4213-ae21-717b6e0874… {"pid": 2423, "job_id": "AJ_cu9HgnhytKJP", "room_id": "RM_WGb5HV4deoEG"} 2025-12-28 135611,551 - ERROR - livekit_ffi:serverroom149livekit ffiserver:room - audio filter cannot be enabled: LiveKit Cloud is required 135611.551 ERROR livekit livekit_ffi:serverroom149:live… - audio filter cannot be enabled: LiveKit Cloud is required {"pid": 2423, "job_id": "AJ_cu9HgnhytKJP", "room_id": "RM_WGb5HV4deoEG"}
t
Thanks for reaching out, Eray. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I see two issues in your logs: the 404 when fetching server settings, and the "audio filter cannot be enabled: LiveKit Cloud is required" error. I can help troubleshoot both — a couple quick clarifying questions first: 1. Are you running LiveKit on LiveKit Cloud or a self‑hosted deployment? 2. Which SDK and version are you using? 3. The logs show room_id "RM_WGb5HV4deoEG" — did this room exist on the target server? Have you recently changed the server URL, API key, or routing/proxy configuration? What you can check right away • If self‑hosted: confirm the server URL in your client matches your server (scheme, hostname, port, path). A 404 means the settings endpoint isn’t reachable at that URL. • If self‑hosted: ensure the LiveKit server is running and HTTP endpoints are exposed (no proxy misrouting). Check server logs around the 404 for the exact requested path. • If using LiveKit Cloud: verify the Cloud instance URL and API key are correct. • For the audio filter: that feature is only available on LiveKit Cloud. If you’re self‑hosting, the audio filter cannot be enabled — use client‑side audio processing or move to LiveKit Cloud to enable it. If you share your deployment type (Cloud vs self‑hosted), server URL (redact secrets), SDK/version, and any recent config changes, I’ll give targeted next steps and commands to check. Sources: Rust SDKs | livekit/livekit_composite | DeepWiki | Voice AI quickstart | LiveKit docs
c
135611.702 WARNI… livekit.…echmatics 
transcription_config
is deprecated. Use individual arguments instead (which override this argument). {"pid": 2423, "job_id":
t
Thanks — I see the new warning about 
transcription_config
being deprecated. Quick guidance and next steps: • The 
transcription_config
argument is deprecated. Use the individual transcription arguments instead (each individual argument overrides the deprecated 
transcription_config
). • Replace the single 
transcription_config
object with the specific options you need (for example: language, enable_partial_results, model, etc.) in your room/session creation or config call. • This change is safe to make now; individual args take precedence so migrating avoids future issues. I still need those earlier details to fully troubleshoot the 404 and audio‑filter errors: 1. Are you on LiveKit Cloud or self‑hosting? 2. SDK and version you're using. 3. Server URL (redact keys) and whether the room ID shown exists on that server. Share those and I’ll provide exact config examples and commands to check.
c
Copy code
stt=speechmatics.STT(
    api_key=os.getenv("SPEECHMATICS_API_KEY"),
    language="tr",
    additional_vocab=additional_vocab,
    end_of_utterance_silence_trigger=0.2,
    operating_point=OperatingPoint.ENHANCED,
    max_delay=0.8,
    end_of_utterance_mode=EndOfUtteranceMode.FIXED,
    transcription_config=TranscriptionConfig(audio_filtering_config={"volume_threshold":3.4, "streaming_mode":True})
),
135611.702 WARNI… livekit.…echmatics 
transcription_config
is deprecated. Use individual arguments instead (which override this argument). {"pid": 2423, "job_id":
t
Thanks — I’m responding to the deprecation warning for 
transcription_config
and the earlier 404 / audio-filter issues. First, update your STT config to pass individual transcription arguments instead of 
transcription_config
. Replace the deprecated field with the equivalent top-level args (these override the old object). Example converted from your snippet:
Copy code
stt = speechmatics.STT(
    api_key=os.getenv("SPEECHMATICS_API_KEY"),
    language="tr",
    additional_vocab=additional_vocab,
    end_of_utterance_silence_trigger=0.2,
    operating_point=OperatingPoint.ENHANCED,
    max_delay=0.8,
    end_of_utterance_mode=EndOfUtteranceMode.FIXED,
    # audio_filtering args moved from transcription_config:
    audio_filtering_volume_threshold=3.4,
    audio_filtering_streaming_mode=True,
)
Use the exact individual option names your SDK exposes (the above names illustrate the mapping: move keys from 
transcription_config["audio_filtering_config"]
into explicit args). Doing this removes the deprecation warning and ensures the individual args take precedence. Reminder on the other errors: • The audio filter cannot be enabled on self‑hosted servers — it requires LiveKit Cloud. • The 404 fetching server settings means the client attempted to call a missing endpoint (check server URL/routing). If you want, share: • Whether you’re on LiveKit Cloud or self‑hosting, • SDK and version, • The server URL (redact keys) and whether the room exists, and I’ll give exact argument names for your SDK and targeted checks for the 404/audio‑filter errors.
c
TypeError: STT.__init__() got an unexpected keyword argument 'audio_filtering_volume_threshold'
t
Thanks — I’m responding to the TypeError and the earlier deprecation/Cloud errors. Short answer: 
audio_filtering_volume_threshold
is not a valid parameter for the 
STT
class. Remove that argument. Audio filtering (enhanced noise cancellation) is only available on LiveKit Cloud — it cannot be enabled on self‑hosted servers. What to do next • Remove the unsupported arg from your STT init. Example for Speechmatics (keep only supported args):
Copy code
stt = speechmatics.STT(
    api_key=os.getenv("SPEECHMATICS_API_KEY"),
    language="tr",
    additional_vocab=additional_vocab,
    end_of_utterance_silence_trigger=0.2,
    operating_point=OperatingPoint.ENHANCED,
    max_delay=0.8,
    end_of_utterance_mode=EndOfUtteranceMode.FIXED,
)
• For the deprecation warning: replace 
transcription_config
usage with the new top‑level or Room input options your SDK exposes (e.g., use 
text_enabled=True
or the provider’s documented args). Individual transcription args override the old config. • If you need audio filtering: ◦ Use LiveKit Cloud (the feature is enabled server‑side there). ◦ If self‑hosting, perform audio processing client‑side or with an external service. If you want, tell me: 1) Cloud vs self‑hosted, 2) SDK and version, 3) the exact STT class you’re using (Speechmatics plugin) and where you were trying to set audio filtering. I’ll provide the exact, supported argument names or the RoomOptions mapping for your SDK. Sources: Turns overview | LiveKit docs | AssemblyAI plugin guide | LiveKit docs | Baseten STT plugin guide | LiveKit docs | Speechmatics STT plugin guide | LiveKit docs | Text and transcriptions | LiveKit docs
7 Views
Open in Slack
PreviousNext
Powered by