Error Codes

RTC General Error Codes

10000

Request successful

Troubleshooting: Interface request successful

40100

Service not activated

Troubleshooting: .

40001

Current user is no longer in the room

Troubleshooting: Please confirm the user's current connection status. Check the connection status in the developer console Polaris.

40003

Room does not exist

Troubleshooting: Please confirm if the room number is correct.

40004

User ID is empty

Troubleshooting: Required parameters cannot be empty.

40005

Room capacity exceeded limit

Troubleshooting: Please confirm if the current number of people in the room exceeds the limit. If you need to adjust the capacity limit, please submit a ticket to contact us.

40007

Token encoding/decoding error

Troubleshooting:

1. RTC token cannot be parsed. Please check the correctness of the token.
2. Please confirm if your client usage flow is correct, or submit a ticket to contact us.

40009

Token request parsing failed

Troubleshooting: Please confirm if your client usage flow is correct, or submit a ticket to contact us.

40010

Token does not have RTC service activated

Troubleshooting:

40011

Incorrect room type for joining

Troubleshooting: Confirm the room type. The room's own type and the type the user is joining are inconsistent.

40012

User is not authorized

Troubleshooting: Only exists in hybrid cloud. Please contact business for processing.

40015

Live streaming merge address is empty

Troubleshooting: Please confirm in the console whether the live streaming service is activated and not in arrears.

40016

Video live streaming not allowed

Troubleshooting: Please confirm in the console whether the live streaming service has enabled audio-only restrictions.

40017

Audio live streaming not allowed

Troubleshooting: Please confirm in the console whether the live streaming service has enabled video-only restrictions.

40018

Failed to generate token

Troubleshooting: Internal service exception. Please provide user ID and time, and submit a ticket to contact us.

40021

User is banned

Troubleshooting: Check user status. You can unban the user.

40022

Invited room for co-anchoring does not exist

Troubleshooting: Please confirm if the room number is correct.

40023

Invited person for co-anchoring is not in the room

Troubleshooting: Please confirm if the user ID is correct.

40024

Co-anchoring person is already being invited

Troubleshooting: Already being invited, cannot invite repeatedly.

40025

Co-anchoring invitation cancelled, but invitation information does not exist

Troubleshooting: Check the invitation information parameters.

40026

Responding to invitation, but invitation information does not exist

Troubleshooting: Check the invitation information parameters.

40027

SessionID inconsistent when responding to invitation

Troubleshooting: When responding, check the passed parameters and confirm if the sessionId is consistent.

40029

Room already exists

Troubleshooting: Room already exists, no need to recreate.

40030

Room type not supported

Troubleshooting: For role switching, room type must be live streaming. The client should pass LIVE_BROADCAST type.

40031

Live streaming role switching failed

Troubleshooting: Because the passed type is incorrect. Currently only supports AnchorToViewer and ViewerToAnchor.

40032

Already joined the room

Troubleshooting: User has already joined the room or user has joined the room on another device.

40033

(Cross-App communication scenario) Allowed intercommunication App or gateway address not configured

Troubleshooting: Needs to be configured in the backend. Please submit a ticket to contact us.

41003

Request parameters incorrect

Troubleshooting: Parameter parsing failed, check the request parameters.

42001

Authentication information missing

Troubleshooting: Check if the App Key in the header, rtcToken and roomId in the body, or client type are empty. These parameters cannot be empty.

42002

Authentication token invalid

Troubleshooting: Usually due to mismatch between private cloud and public cloud, or user has been in the room for too long, network issues causing internal refresh failure.

42003

Room authentication failed

Troubleshooting: Authentication token and request information do not match. Please submit a ticket to contact us.

43001

Request content parsing failed

Troubleshooting: Please check the validity of the parameters. If there are no issues, please provide user ID and operation time, and submit a ticket to contact us.

43002

Media SDP parsing failed

Troubleshooting: Usually internal SDP generation exception. Please submit a ticket to contact us.

45008

Live streaming LiveURL parsing failed

Troubleshooting: Please confirm if this LiveURL is obtained from our platform and complete, and confirm if the format is correct.

45011

Live streaming LiveURL expired

Troubleshooting: Whether the live streaming room corresponding to this LiveURL has adjusted the room type: audio-only, audio-video.

45013

Live streaming configuration information incorrect

Troubleshooting:

1. Please check if Console RTC-related services are activated.
2. If the service is activated and the time interval is more than 15 minutes, but there are still issues, please submit a ticket to contact us.

45015

Current client version does not support UDP obfuscation

Troubleshooting: Used for specific regional features. Please contact business.

Live Streaming

Range: 46000–46999, 48000–48999

46100

Live streaming not activated

Troubleshooting: Need to contact business for activation.

46001

Request method incorrect

Troubleshooting: Refer to the corresponding API description: POST/GET.

46002

Request parameter type incorrect

Troubleshooting: Request Content-Type must be application/json.

46004

Request parameters incorrect

Troubleshooting: Refer to the required parameters description of the corresponding API.

46005

Live streaming configuration information incorrect

Troubleshooting: The config parameter in the request parameters failed to parse. Please carefully check the config parameter.

46006

Request URL does not exist

Troubleshooting: The requested interface address does not exist. Please check the request address.

46007

Authentication token invalid

Troubleshooting: RTC token cannot be parsed. Please check the correctness of the token.

46010

Room number does not exist or specified user is not in the room

Troubleshooting: Please check if your user and room IDs are correct. If there are still issues, please submit a ticket to contact us.

46011

Custom layout configuration parameter error

Troubleshooting: Custom layout parameters have issues. rtcToken or version is empty.

46013

Live streaming room has reached maximum capacity limit

Troubleshooting: Please confirm if the current number of people in the room exceeds the limit. If you need to adjust the capacity limit, please submit a ticket to contact us.

46016

Live streaming room has been destroyed

Troubleshooting: The live streaming room has been destroyed. Check if the server has called Destroy Room.

46020

Custom layout configuration parameter error

Troubleshooting: Please check the correctness and validity of the layout parameters.

48001

CDN push stream address format error

Troubleshooting: CDN push address cannot be empty. The address must start with rtmp:// or rtmps://.

48002

CDN push stream error

Troubleshooting: CDN push stream address has issues. Check the correctness and connectivity of the address.

48004

Current room's CDN push stream address exceeds limit

Troubleshooting: Maximum 5 push streams.

48006

Subscribed RTC URI format error

Troubleshooting: Auto-subscription is set, no need to call manually.

48500

Service reserved internal error

Troubleshooting: If encountered, please submit a ticket with relevant context logs. We will investigate promptly.

Cloud Recording & Screenshot

Note

Range: 47000–47999

47100

Service not activated

Troubleshooting:

47002

Stream specified in recording HTTP request does not exist

Troubleshooting: The user's corresponding stream does not exist. Check if the client user has pushed streams. After confirmation, please submit a ticket to contact us.

47003

Recording task already exists

Troubleshooting: The recording that has been started will have callbacks. You can check the callback information.

47004

Alibaba Cloud OSS bucket information error

Troubleshooting: Failed to get OSS bucket information. Specific error information will be shown when operating the bucket. Check the OSS configuration information.

47005

Alibaba Cloud OSS bucket information error

Troubleshooting: Failed to get OSS bucket information. Specific error information will be shown when operating the bucket. Check the OSS configuration information.

47006

Failed to upload file to Alibaba Cloud OSS

Troubleshooting: Specific error details need to be checked on the server side. Please submit a ticket to contact us.

47007

Tencent Cloud COS initialization failed

Troubleshooting: Need to check specific COS error information on the server side. Please submit a ticket to contact us.

47008

Tencent Cloud COS bucket information error

Troubleshooting: Tencent Cloud COS bucket information error. Please check the COS configuration information.

47009

Failed to upload file to Tencent Cloud COS

Troubleshooting: Specific error details need to be checked on the server side. Please submit a ticket to contact us.

47012

Failed to upload file to Amazon S3

Troubleshooting: Please check the S3 configuration information and test if upload is possible.

47015

Failed to upload file to Qiniu Cloud Kodo

Troubleshooting: Please check the Kodo configuration information and test if upload is possible.

47017

This third-party storage vendor is not supported

Troubleshooting: Currently supports Alibaba Cloud, Tencent Cloud, Huawei Cloud, Kingsoft Cloud, Wangsu, and Youpai Cloud.

47019

Failed to upload to third-party storage, retrying

Troubleshooting: Previous upload failed, currently retrying.

47020

Failed to upload to third-party storage, retry exceeded 24 hours, cache file deleted

Troubleshooting: File upload failure needs investigation. Please submit a ticket to contact us.

47025

Service reserved internal error

Troubleshooting: If encountered, please submit a ticket with relevant context logs. We will investigate promptly.

47031

Manual recording mode not enabled

Troubleshooting: Need to enable Modify Trigger Conditions in Cloud Recording in the developer console.

47032

Manual recording request configuration parameters error

Troubleshooting: Please check the request parameters and parameter format.

47034

MCU stream does not exist

Troubleshooting: If MCU stream merging recording is selected, MCU streams are required. Please check the client.

47116

Manual recording request room does not exist

Troubleshooting: Please check if the room ID is correct, or if the room ID has been destroyed.

47117

Manual recording request user does not exist

Troubleshooting: Please check the correctness of the user ID and whether the user has joined the room.

47118

Manual recording request information error

Troubleshooting: Check that room ID, App Key, and sessionId cannot be empty.

47120

Manual recording request SessionId is empty

Troubleshooting: sessionId cannot be empty.

Content Moderation

Range: 49000–49999

49007

Token verification failed

Troubleshooting: Please check if the rtctoken is correct.

49008

Invalid App Key

Troubleshooting: Please check if the App Key is correct. The signature parameters need to be placed in the header.

49009

Room or user does not exist

Troubleshooting: Please check that the room ID and user ID parameters are not empty. Note that the room ID should be placed in the header.

49014

Mode error, calling manual interface in automatic mode

Troubleshooting: The RTC Moderation trigger mode needs to be configured as manual to use the API to control moderation tasks.

49015

The userId or streamId to be moderated does not exist in the room

Troubleshooting: Please check the correctness of userId and streamId.

49016

Calling stop interface without starting moderation

Troubleshooting: Please start moderation first before stopping it.

49017

Start moderation parameter format error

Troubleshooting: Please check that the request parameters users and streams are not empty and need to be arrays.

49018

Stop moderation parameter format error

Troubleshooting: Please check that the request parameters users and streams are not empty and need to be arrays.

49202

Moderation request HTTP failed

Troubleshooting: The moderation server is unavailable. Please submit a ticket to contact us.

49600

Request interface restricted

Troubleshooting: Request to third-party moderation interface is restricted. Please submit a ticket to contact us.

49601

Invalid parameters

Troubleshooting: Request to third-party moderation interface has invalid parameters. Please submit a ticket to contact us.

49602

Service failed

Troubleshooting: Request to third-party moderation service failed. Please submit a ticket to contact us.

49603

Audio stream count exceeded limit

Troubleshooting: Audio stream count exceeded limit. Please submit a ticket to contact us.

49610

Insufficient balance

Troubleshooting: Please check if your Shumei fees are sufficient.

49611

No permission to operate

Troubleshooting: No permission for moderation. You need to communicate with Shumei.