Agora cloud recording stop api always giving 404 response
Asked Answered
F

2

7

https://api.agora.io/v1/apps/${config.agoraAppId}/cloud_recording/resourceid/${meetingComplete.resourceId}/sid/${meetingComplete.sid}/mode/mix/stop api getting below response always

 {
    resourceId: '',
    sid: '',
    code: 404,
    serverResponse: {
      command: 'StopCloudRecorder',
      payload: { message: 'Failed to find worker.' },
      subscribeModeBitmask: 1,
      vid: ''
    }
  }
}
Fluoride answered 27/11, 2021 at 7:16 Comment(0)
F
2

The issue due to s3 bucket region specified in agora cloud recording start api mismatching with s3 bucket region in aws.

Fluoride answered 18/12, 2021 at 12:22 Comment(0)
B
2

A 400 response from stop means your original request for start was properly formatted and successfully making the call to start the Agora Cloud Recorder instance but something caused the Agora Cloud Recorder worker to fail to start, so when you call stop there is nothing to stop because nothing actually started.

Have you tried using the Agora Postman collection to test? I would recommend using it within Postman because it offers a working config that requires you to set your connection credentials into the variables and it should work if your bucket is properly configured.

I wrote this quick-start guide on how to set up Cloud Recording and use the Postman collection to test that your storage bucket is properly configured.

Buote answered 2/12, 2021 at 20:21 Comment(3)
The issue due to s3 bucket region specified in agora cloud recording start api mismatching with s3 bucket region in aws.Fluoride
Glad to hear you figured out the issue. Is it working now?Buote
yes, it working now. Thanks for the answer my question.Fluoride
F
2

The issue due to s3 bucket region specified in agora cloud recording start api mismatching with s3 bucket region in aws.

Fluoride answered 18/12, 2021 at 12:22 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.