zed-industries/zed · error

POST {} failed with status code {:?}, {:?}

Error message

POST {} failed with status code {:?}, {:?}

What it means

LiveKit API POST request returned a non-success HTTP status; the status and response body are formatted into this error. Raised from the generic request helper used by create_room, delete_room, remove_participant, and update_participant.

Source

Thrown at crates/livekit_api/src/livekit_api.rs:104

        );
        let url = format!("{}/{}", self.url, path);
        log::info!("Request {}: {:?}", url, body);
        async move {
            let token = token?;
            let response = client
                .post(&url)
                .header(CONTENT_TYPE, "application/protobuf")
                .bearer_auth(token)
                .body(body.encode_to_vec())
                .send()
                .await?;

            if response.status().is_success() {
                log::info!("Response {}: {:?}", url, response.status());
                Ok(Res::decode(response.bytes().await?)?)
            } else {
                log::error!("Response {}: {:?}", url, response.status());
                anyhow::bail!(
                    "POST {} failed with status code {:?}, {:?}",
                    url,
                    response.status(),
                    response.text().await
                );
            }
        }
    }
}

#[async_trait]
impl Client for LiveKitClient {
    fn url(&self) -> &str {
        &self.url
    }

    async fn create_room(&self, name: String) -> Result<()> {
        let _: proto::Room = self

View on GitHub (pinned to f4178619ac)

Solutions

1. Verify the LiveKit server URL and that the service is reachable
2. Check authentication/token generation for expiry or wrong key
3. Retry the request; transient 5xx errors often resolve
4. Inspect the logged status and body for the server-side cause

When it happens

Trigger: Thrown at crates/livekit_api/src/livekit_api.rs:104 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20). Data as JSON: /api/errors/c8e1512376162657. Report an issue: GitHub.