logo
Live Streaming
On this page

Common Error codes

2025-01-21

Introduction

When the SDK encounters errors related to network or media issues, the SDK cannot recover automatically and requires App intervention or user notification. If error information exists in the return result after calling an interface, error information exists in event callbacks, or error logs appear in console logs, it indicates an exception in the interface call.

  • Example code for error information returned after calling an interface:
const { errorCode, extendedData } = await zg.setCaptureVolume(stream, result);
// errorCode is the error code, extendedData is the error description
console.log(errorCode, extendedData);
  • Example code for error information thrown after calling an interface:
try {
    await zg.setCaptureVolume(stream, result);
} catch (error) {
    // errorCode is the error code, extendedData is the error description
    const { errorCode, extendedData } = error;
    console.log(errorCode, extendedData);
}
  • Example code for error information in event callbacks:
zg.on('roomStateChanged', (roomID, reason, errorCode, extendedData) => {
    if (errorCode !== 0) {
      // errorCode is the error code, extendedData is the error description
      console.log(errorCode, extendedData);
    }
})

1000xxx/1100xxx Common Error codes

Common error codes are for general interface errors, usually occurring when calling startPublishingStream and startPlayingStream interfaces. Please handle them according to the following error codes.

Error codeDescription
0Execution successful.
1000002Description: Not logged in to the Room.
Possible cause: Not logged in to the Room or the Room was disconnected abnormally.
Suggestion: Please call loginRoom to log in to the Room before calling Stream publishing or playing.
1000014Description: Input StreamID is too long.
Possible cause: The StreamID parameter length exceeds the limit when calling startPublishingStream or startPlayingStream.
Suggestion: StreamID supports a maximum of 256 characters. Check if the StreamID parameter passed when calling the function is too long.
1000015Description: Input Stream ID is empty.
Possible cause: The StreamID parameter passed when calling startPublishingStream or startPlayingStream is undefined, null, or an empty string.
Suggestion: Check if the streamID parameter passed when calling the function is normal.
1000016Description: Input Stream ID contains illegal characters.
Possible cause: The StreamID passed when calling startPublishingStream or startPlayingStream contains illegal characters.
Suggestion: Check if the StreamID parameter passed when calling the function is normal. Only numbers, English characters, and "-", "_" are supported.
1000017Description: Network disconnected.
Possible cause: Network exception or media negotiation failure during Stream publishing/playing.
Suggestion: Check if the network is normal.
1000018Description: Local stream error.
Possible cause: Web error code. The passed stream object is incorrect or the stream object was not created by the SDK.
Suggestion: Web: Check if the printed stream object is normal and confirm if it was generated by the createStream interface. Generally occurs in destroyStream, setVideoConfig, useVideoDevice, useAudioDevice interfaces.
1000019Description: Failed to get sound level.
Possible cause: Failed to get sound level.
Suggestion: Generally a browser compatibility issue. Please try switching browsers.
1100001Description: Parameter error.
Possible cause: Incorrect parameter passed.
Suggestion: Check the printed parameter passed and view the specific error field in extendedData.
1100002Description: Request response timeout.
Possible cause: SDK request to server timed out, possibly due to network reasons.
Suggestion: Please try switching networks.
1100003Description: Socket closed.
Possible cause: Possibly due to network reasons causing the socket connection between SDK and server to be closed.
Suggestion: Please try switching networks.
1100999Description: Server unknown error.
Possible cause: Generally a server error.
Suggestion: Please contact ZEGOCLOUD technical support.

1001xxx/1101xxx Debugging Phase Error codes

Debugging phase error codes refer to errors that developers are prone to encounter during application development, usually manifested as interface parameter errors.

Error codeDescription
1001004Description: Authentication failed.
Possible cause: AppID is incorrect.
Suggestion: Check if the passed AppID matches the AppID in the ZEGOCLOUD Console.
1001021Description: Failed to set geofencing.
Possible cause: Setting geofencing after creating engine instance.
Suggestion: Set geofencing before creating engine instance.
1101000Description: SDK initialization failed.
Possible cause: Caused by incorrect AppID.
Suggestion: Please check if AppID is correct
1101001Description: WeChat Mini Program getSetting method call failed, unable to detect if camera and microphone functions are normal.
Possible cause: Mini program initialization failed, WeChat version too low, or Stream publishing/playing component permissions not obtained.
Suggestion: Please try upgrading WeChat version and check if there are component permissions.
1101002Description: Failed to get streaming service configuration.
Possible cause: Failed to get streaming service configuration.
Suggestion: Please contact ZEGOCLOUD technical support.

Errors occur when calling the loginRoom interface, usually Room login parameter errors, or exceptions in communication between SDK and ZEGO Room server.

Error codeDescription
1002001Description: Number of logged in Rooms exceeds limit.
Possible cause: Currently only supports logging in to 1 main Room and 1 multi-Room simultaneously.
Suggestion: Please check if the current user has logged in to too many Rooms.
1002002Description: Not logged in with this Room ID.
Possible cause: Before calling [logoutRoom] or [switchRoom] or [renewToken] or [setRoomExtraInfo], not logged in with this Room ID.
Suggestion: Check if logged in with this Room ID.
1002005Description: Input user ID is empty.
Possible cause: The input user ID is an empty string or no user ID was input.
Suggestion: Check if the user ID is empty.
1002006Description: Input user ID contains illegal characters.
Possible cause: Input user ID contains illegal characters.
Suggestion: Please check if the user ID is correct. User ID is a string with maximum of 64 bytes, only supporting numbers, English characters, and '~', '!', '@', '#', '$', '', '^', '&', '*', '(', ')', '_', '+', '=', '-', ';', '', ',', '.'.
1002007Description: Input user ID is too long.
Possible cause: Input user ID is too long.
Suggestion: Please check if the user ID is too long, maximum length should be less than 64 bytes.
1002008Description: Input user name is empty.
Possible cause: Input user name is empty.
Suggestion: Please check if the user name is empty.
1002010Description: Input user name is too long.
Possible cause: Input user name is too long.
Suggestion: Please check if the input user name is too long, maximum length should be less than 256 bytes.
1002011Description: Input Room ID is empty.
Possible cause: Input Room ID is empty.
Suggestion: Please check if the Room ID is empty.
1002012Description: Input Room ID contains illegal characters.
Possible cause: Input Room ID contains illegal characters.
Suggestion: Only supports numbers, English characters, and '~', '!', '@', '#', '$', '', '^', '&', '*', '(', ')', '_', '+', '=', '-', ', ';', '', ',', '.', '<', '>', '/' .
1002013Description: Input Room ID is too long.
Possible cause: Input Room ID is too long.
Suggestion: Please check if the input Room ID is too long, maximum length should be less than 128 bytes.
1002014Description: Room not logged in or Room has been disconnected.
Possible cause: The current Room does not exist.
Suggestion: Please contact ZEGOCLOUD technical support.
1002015Room extra information key is too long.
The Room extra information key input in the [setRoomExtraInfo] function is greater than or equal to 128 bytes.
Please check the Room extra information key input when calling the [setRoomExtraInfo] function to ensure its length is less than 128 bytes.
1002016Room extra information value is too long.
The Room extra information value input in the [setRoomExtraInfo] function is greater than or equal to 128 bytes.
Please check the Room extra information value input when calling the [setRoomExtraInfo] function to ensure its length is less than 128 bytes.
1002017Description: The number of keys set for Room extra messages exceeds the maximum supported limit.
Possible cause: Different keys were passed when calling the [setRoomExtraInfo] interface multiple times.
Suggestion: Currently only supports one key.
1002018Description: In multi-Room mode, the logged in user ID or user name is not the same.
Possible cause: In multi-Room mode, different user IDs or user names were passed when logging in to multiple Rooms.
Suggestion: In multi-Room mode, the passed user ID or user name must be the same.
1002031Description: Room login timeout.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1002034Description: Number of users logging in to the Room exceeds the maximum.
Possible cause: The number of users logging in to the Room exceeds the maximum user limit configured for the Room (default maximum Room users in test environment is 50, unlimited in production environment).
Suggestion: Please contact ZEGOCLOUD technical support to check if the number of Room users exceeds the limit.
1002036Description: Login failed, multi-Room feature not enabled.
Possible cause: Multi-Room feature not enabled.
Suggestion: Please contact ZEGOCLOUD technical support.
1002037Description: Total number of simultaneously logged in Rooms exceeds limit.
Possible cause: Multi-Room feature has a limit on the total number of Rooms that can be logged in simultaneously.
Suggestion: Please contact ZEGOCLOUD technical support.
1002050Description: User kicked out of Room.
Possible cause: Possibly the same user ID logged in on another device.
Suggestion: Please contact ZEGOCLOUD technical support.
1002053Description: Retrying Room login exceeded maximum retry time.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1002055Description: Business backend sent kickout Room signal.
Possible cause: Client called server kickout interface, triggering server to send kickout signal.
Suggestion: Please check the kickout reason and contact ZEGOCLOUD technical support.
1002056Description: User performed duplicate login.
Possible cause: Logging in to main Room again without logging out of main Room.
Suggestion: Please troubleshoot the login logic. It is recommended to set breakpoints or print at the login and logout logic for debugging.
1002064Description: Room ID is already used by the login Room interface. Before leaving the Room, the current user cannot log in to this Room again.
Possible cause: Room ID is already used by the login Room interface.
Suggestion: Leave the Room with the same Room ID.
1002099Description: Room login failed due to system internal exception.
Possible cause: Server returned an undefined error code, error information is in extendedData.
Suggestion: Please contact ZEGOCLOUD technical support.
1102001Description: Heartbeat timeout.
Possible cause: Possibly due to network reasons. Default heartbeat timeout is triggered when no Room heartbeat response is received within 90 seconds.
Suggestion: Please try switching networks and retry.
1102011Description: Data format error.
Possible cause: Data format error.
Suggestion: Please contact ZEGOCLOUD technical support.
1102012Description: Login process is in progress.
Possible cause: Room login is in progress.
Suggestion: Contact ZEGOCLOUD technical support.
1102013Description: Room signaling request error.
Possible cause: Possibly due to network reasons.
Suggestion: Try switching networks and retry or contact ZEGOCLOUD technical support.
1102014Description: ZPush failed.
Possible cause: ZPush failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1102015Description: User login state error.
Possible cause: Login state error.
Suggestion: Please contact ZEGOCLOUD technical support.
1102016Description: Login token format is incorrect
Possible cause: Login token format is incorrect.
Suggestion: Token acquisition method: For Web, refer to User Permission Control. For Mini Program, refer to User Permission Control.
1102017Description: Dispatch failed.
Possible cause: Media node dispatch failed.
Suggestion: Please take the error code from the Stream publishing/playing status callback and contact ZEGOCLOUD technical support.
1102018Description: Login token expired.
Possible cause: Login token expired. This error may also occur during Stream publishing/playing process.
Suggestion: Timely call the renewToken interface to update the token.
1102019Description: subcmd error.
Possible cause: subcmd error.
Suggestion: Please contact ZEGOCLOUD technical support.
1102020Description: Login authentication failed.
Possible cause: Login authentication failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1102021Description: biz_channel error.
Possible cause: biz_channel error.
Suggestion: Please contact ZEGOCLOUD technical support.
1102022Description: Call request timeout.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1102023Description: Failed to connect to media server.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1102025Description: Local log report failed.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.

After calling the Stream publishing interface, or if an exception occurs during Stream publishing, developers can obtain relevant error codes from the publisherStateUpdate callback. Please handle them according to the following error codes.

Handling non-zero error codes in Stream publishing callback:

  1. When "state" is "NO_PUBLISH" and "errorCode" is not 0, it indicates Stream publishing failed and will not retry Stream publishing. At this point, a Stream publishing failure notification can be displayed in the interface.
  2. When "state" is "PUBLISH_REQUESTING" and "errorCode" is not 0, it indicates retrying Stream publishing. If Stream publishing is not successful after exceeding the retry time, a Stream publishing failure notification will be thrown.
Error codeDescription
1003025Description: ZEGO backend prohibits Stream publishing.
Possible cause: Stream publishing authentication is enabled and the Stream is prohibited by the media server.
Suggestion: If not prohibited by the developer calling the interface, please contact ZEGOCLOUD technical support to resolve.
1003028Description: Stream publishing failed, same Stream already exists in the Room.
Possible cause: Same Stream already exists in the Room.
Suggestion: Change to a new Stream ID. Adjust Stream name generation strategy to ensure uniqueness.
1003040Description: Failed to update CDN relay status.
Possible cause: Relay URL is incorrect.
Suggestion: Check if the input URL is valid.
1003050Description: Stream extra information is null.
Possible cause: Stream extra information is null.
Suggestion: Please check if the stream extra information is normal.
1003051Description: Stream extra information is too long.
Possible cause: Stream extra information is too long.
Suggestion: Please check if the corresponding stream extra information is too long, maximum is 128 bytes.
1103001Description: Stream publishing parameter error.
Possible cause: Stream publishing parameter error.
Suggestion: View the specific error field in the extendedData of the parameter error.
1103002Description: Browser not supported.
Possible cause:
  1. Not accessed via https or localhost.
  2. Browser version not supported.

Suggestion:
  1. Please deploy the project under an https server or use localhost access.
  2. If the above issues cannot be resolved, please replace or upgrade the browser.
1103003Description: Media connection failed.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1103010Description: Screen sharing failed.
Possible cause: Screen Stream publishing failed, parameter device not supported, using plugin publishing but plugin not installed. View specific error information in extendedData.
Suggestion: Please contact ZEGOCLOUD technical support.
1103011Description: Device information enumeration failed.
Possible cause: Failed to enumerate devices when getting device list.
Suggestion: Get the specific error information in console and contact ZEGOCLOUD technical support.
1103019Description: Stream publishing authentication error.
Possible cause: streamParams in Stream publishing parameters set incorrectly causing Stream playing authentication failure.
Suggestion: Check if the token in streamParams is correct and if the string concatenation is correct.
1103020Description: Failed to get media service address.
Possible cause: Failed to get media service address.
Suggestion: Get the specific error information in console and contact ZEGOCLOUD technical support.
1103021Description: Media service connection failed.
Possible cause: Stream publishing/playing and media creation session failed.
Suggestion: Get the specific error information in console and contact ZEGOCLOUD technical support.
1103022Description: Offer creation failed.
Possible cause: Browser incompatibility.
Suggestion: Switch browsers or get the specific error information in console and contact ZEGOCLOUD technical support.
1103023Description: Failed to set local SDP.
Possible cause: Browser incompatibility.
Suggestion: Switch browsers or get the specific error information in console and contact ZEGOCLOUD technical support.
1103024Description: SDP send failed.
Possible cause: mediaDesc interaction with gateway failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1103025Description: Remote SDP error.
Possible cause: Browser incompatibility.
Suggestion: Switch browsers or get the specific error information in console and contact ZEGOCLOUD technical support.
1103026Description: Candidate information error used by webrtc connection.
Possible cause: Candidate interaction with gateway failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1103027Description: Media connection closed.
Possible cause: SDK disconnected from gateway.
Suggestion: Please contact ZEGOCLOUD technical support.
1103028Description: Ice connection failed.
Possible cause: UDP disconnected, possibly due to network reasons or gateway actively disconnected.
Suggestion: Try switching networks and retry, or contact ZEGOCLOUD technical support.
1103029Description: Stream publishing parameter setting error.
Possible cause: 1. Problem with parameters 2. Device does not support the set parameters.
Suggestion: Get the specific error information in console and contact ZEGOCLOUD technical support.
1103030Description: Stream publishing failed retry timeout.
Possible cause: Possibly due to network reasons causing negotiation timeout or unknown issue blocking the process.
Suggestion: Please try switching networks and retry, or contact ZEGOCLOUD technical support.
1103040Description: Modify parameters when not publishing stream.
Possible cause: Stream not found when changing Stream publishing parameters, possibly because not publishing when calling.
Suggestion: Please check if there is stream publishing when calling.
Note: This error code means "Current stream publishing quality is poor or network is poor, please check your network" in versions before 3.0.0.
1103041Description: Device plugged or unplugged or loose.
Possible cause: Device plugged or unplugged or loose.
Suggestion: Check if the device is plugged in properly or has poor contact.
1103042Description: User actively canceled screen sharing.
Possible cause: Actively clicked cancel when selecting in the popup during screen sharing.
Suggestion: Please check if this meets the current business logic. If so, no need to resolve.
1103043Description: Current browser does not support screen sharing.
Possible cause: Current browser does not support creating screen stream.
Suggestion: Update or switch browsers.
1103044Description: Stream not created by createStream.
Possible cause: Web error, stream not generated by createStream interface.
Suggestion: Web:
1. Clarify the source of the stream and ensure it is generated by createStream interface.
2. createStream is an asynchronous operation that returns a promise. Need to ensure stream publishing after then or await.
1103045Description: Media stream does not contain video.
Possible cause: Stream did not contain video track when switching devices, generally occurs when calling switchDevice interface, using parameter video
when creating stream.
Suggestion: Please check if the stream contains video track.
1103046Description: Media stream does not contain audio.
Possible cause: Stream did not contain audio track when switching devices, generally occurs when calling switchDevice interface, using parameter audio
when creating stream.
Suggestion: Please check if the stream contains audio track.
1103047Description: MediaStreamTrack object not found.
Possible cause: Stream did not contain the corresponding type track when modifying parameters, generally occurs in Web when calling replaceTrack interface.
Suggestion: Please check if the stream contains the corresponding type track, or contact ZEGOCLOUD technical support.
1103048Description: Device not found.
Possible cause: Device ID does not exist when switching devices, possibly occurs when calling switchDevice interface or passing incorrect parameters when creating stream.
Suggestion: Please check if the device ID exists, or contact ZEGOCLOUD technical support.
1103049Description: Duplicate playing of the same stream.
Possible cause: Possibly duplicate stream playing or previous stream playing not stopped.
Suggestion: Please check if the stream playing logic is correct and confirm if there is duplicate stream playing.
1103050Description: Websocket disconnected.
Possible cause: Possibly network problem causing media node socket disconnect.
Suggestion: Please try switching networks and retry.
1103051Description: Stream publishing retry timeout.
Possible cause: Generally network reasons.
Suggestion: Please try switching networks and retry. If occurring frequently, please contact ZEGOCLOUD technical support.
1103052Description: CDN Stream publishing error.
Possible cause: Possibly incorrect CDN relay type parameter, cdnPublishConfig.type=["addpush"
1103053Description: Must use HTTPS protocol.
Possible cause: webrtc official only allows HTTPS requests for devices.
Suggestion: Request using HTTPS.
1103054Description: No preview.
Possible cause: Stream publishing does not exist when modifying Stream publishing parameters and status.
Suggestion: Troubleshoot stream publishing logic to ensure calling after successful stream publishing. Check if parameters are correct.
1103055Description: Stream publishing not found.
Possible cause: Stream publishing not found, error occurs when setting stream extra information and relaying to CDN (dynamic relay).
Suggestion: Troubleshoot stream publishing logic to ensure calling after successful stream publishing. Check if there are problems with parameters.
1103056Description: Currently publishing stream.
Possible cause: Duplicate stream publishing or previous stream publishing not stopped.
Suggestion: Please check if the stream publishing logic is correct.
1103057Description: Local mixing audio effect resource decoding failed.
Possible cause: Audio resource format incorrect or browser incompatibility.
Suggestion: Try switching browsers or contact ZEGOCLOUD technical support.
1103058Description: Client IP changed.
Possible cause: Client IP changed.
Suggestion: Check if the client IP has changed.
1103059Description: Stream publishing network node expired.
Possible cause: Stream publishing network node expired.
Suggestion: Contact ZEGOCLOUD technical support.
1103060Description: Session request timeout.
Possible cause: Session request timeout.
Suggestion: Try switching networks and retry or contact ZEGOCLOUD technical support.
1103061Description: Failed to get media.
Possible cause:
1. In iPhone 12.1 version, when creating stream, if parameters are not within device parameters, an error may occur, for example, phone only has 720p, but createStream interface parameter passed 1080p resolution.
2. Error when creating stream: NotReadableError, could not start audio source.
Suggestion: 1. Check parameters for creating stream. 2. Get error information in console and contact ZEGOCLOUD technical support.
1103064Description: Media stream has no device permissions.
Possible cause: Media stream has no device permissions, generally Web interface createStream error.
Suggestion: Check if device permissions are granted.
1103065Description: Device not available for capturing media stream.
Possible cause: Possibly your current camera or microphone is occupied by another application.
Suggestion: Check if camera or microphone is being occupied.
1103066Description: Device parameters error when creating stream.
Possible cause: Device parameters error when creating stream or device cannot meet requirements.
Suggestion: Try checking or changing parameters and retry.
1103072Description: Does not support enabling beauty feature.
Possible cause: Your current browser does not support beauty feature.
Suggestion: Please refer to browser compatibility instructions in Basic Beauty and use the corresponding browser version to enable beauty feature.
1103073Description: Beauty feature is starting.
Possible cause: Because setting beauty interface is executed asynchronously, when beauty feature of media stream is not fully enabled, calling startPublishingStream interface to publish stream, stream publishing picture cannot be expected to be beauty picture.
Suggestion: If you need to enable beauty before stream publishing, you need to wait for beauty asynchronous startup to complete before calling stream publishing interface to publish stream. Refer to example code in Basic Beauty.
1103074Description: Current video track does not support enabling beauty.
Possible cause: Current video track does not support enabling beauty, error occurs at startup, SDK will close beauty.
Suggestion: Try changing device or video track and retry or contact ZEGOCLOUD technical support.
1103075Description: Beauty performance overload.
Possible cause: Beauty performance overload.
Suggestion: Picture will stutter when beauty performance is overloaded. SDK will not close beauty. Developers can decide whether to close beauty feature.
1103080Description: AI noise reduction runtime error.
Possible cause: AI noise reduction error at runtime.
Suggestion: Please contact ZEGOCLOUD technical support.
1103081Description: Does not support AI noise reduction.
Possible cause: Possibly because current browser does not support some APIs, causing AI noise reduction initialization operation to fail
Suggestion: Use latest version of Google Chrome browser and Edge browser.
1103082Description: AI noise reduction performance overload.
Possible cause: AI noise reduction overload.
Suggestion: Audio stuttering or audio-video desynchronization will occur when AI noise reduction is overloaded. SDK will not close AI noise reduction. Developers can decide whether to close AI noise reduction feature.

After calling the Stream playing interface, or if an exception occurs during Stream playing, developers can obtain relevant error codes from the playerStateUpdate Stream playing status callback. Please handle them according to the following error codes.

Error codeDescription
1004002Description: Stream playing failed.
Possible cause: Stream does not exist.
Suggestion: Please check if remote stream publishing is indeed successful, or if stream publishing and playing environments are inconsistent.
1004020Description: Stream playing temporarily interrupted.
Possible cause: Network exception.
Suggestion: Please wait or check network environment.
1004025Description: Stream playing failed.
Possible cause: The Stream is configured as prohibited from publishing by backend system.
Suggestion: Please contact technical support to resolve.
1004099Description: Stream playing failed due to system internal exception.
Possible cause: SDK internal error.
Suggestion: Please contact ZEGOCLOUD technical support.
1104001Description: Stream playing parameter error.
Possible cause: Stream playing parameter error.
Suggestion: Please try checking if the parameters printed in console are correct. You can view specific error fields in extendedData.
1104020Description: Failed to get media service address.
Possible cause: Media node dispatch failed, possibly due to network problems.
Suggestion: Try switching networks and retry. If cannot be resolved, contact ZEGOCLOUD technical support.
1104021Description: Media service connection failed.
Possible cause: Stream publishing/playing and media creation session failed.
Suggestion: Contact ZEGOCLOUD technical support.
1104022Description: Offer creation failed.
Possible cause: Possibly due to browser incompatibility.
Suggestion: Please try switching or upgrading browsers and retry.
1104023Description: Failed to set local SDP.
Possible cause: Possibly due to browser incompatibility.
Suggestion: Please try switching or upgrading browsers and retry.
1104024Description: SDP send failed.
Possible cause: mediaDesc interaction with gateway failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1104025Description: Remote SDP error.
Possible cause: Possibly due to browser incompatibility.
Suggestion: Please try switching or upgrading browsers and retry.
1104026Description: Candidate error.
Possible cause: Candidate interaction with gateway failed.
Suggestion: Please contact ZEGOCLOUD technical support.
1104027Description: Media connection closed.
Possible cause: SDK disconnected from gateway.
Suggestion: Please contact ZEGOCLOUD technical support.
1104028Description: Ice connection failed.
Possible cause: Generally 1. Network reasons 2. Gateway actively disconnected.
Suggestion: Please try switching networks and retry or contact ZEGOCLOUD technical support.
1104029Description: Disconnected from media service.
Possible cause: Generally due to network reasons.
Suggestion: Please try switching networks and retry.
1104030Description: Server negotiation timeout.
Possible cause: Possibly due to network reasons or unknown issue blocking the process.
Suggestion: Please try switching networks and retry or contact ZEGOCLOUD technical support.
1104031Description: Stream playing failed retry timeout.
Possible cause: Media node connection failed, generally network reasons.
Suggestion: Please try switching networks and retry or contact ZEGOCLOUD technical support.
1104032Description: Already playing stream.
Possible cause: Duplicate stream playing or previous stream playing not stopped.
Suggestion: Please try troubleshooting if stream playing logic is correct.
1104033Description: Client IP changed.
Possible cause: Client IP changed.
Suggestion: Please check if the client IP has changed.
1104034Description: Stream playing network node expired.
Possible cause: Stream playing network node expired.
Suggestion: Please contact ZEGOCLOUD technical support.
1104035Description: Reset session push.
Possible cause: Reset session push.
Suggestion: Please contact ZEGOCLOUD technical support.
1104036Description: Request session timeout.
Possible cause: Generally due to network reasons.
Suggestion: Please try switching networks and retry.
1104037Description: Quality detection timeout.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1104038Description: Current AppID does not support L3 (Low-Latency Live Streaming) mode stream playing.
Possible cause: Unsupported resource mode, indicating current AppID does not support L3 (Low-Latency Live Streaming) mode stream playing.
Suggestion: If needed, please contact ZEGOCLOUD technical support to enable.
1104039Description: Stream playing does not exist. In Mini Program, this error code indicates stream playing failed.
Possible cause: Possibly duplicate stream playing or Room does not exist.
Suggestion: Please check if there is duplicate stream playing or Room does not exist.
1104046Description: Stream playing authentication error.
Possible cause: streamParams in Stream playing parameters set incorrectly causing stream playing authentication failure.
Suggestion: Check if the token in streamParams is correct and if the string concatenation is correct.

Errors that may occur in the return results when calling start mixing startMixerTask and stop mixing stopMixerTask interfaces.

Error codeDescription
1005000Description: No mixing service.
Possible cause: Current AppID has no mixing service.
Suggestion: If needed, please contact ZEGOCLOUD technical support to enable.
1005001Description: Mixing task ID is empty.
Possible cause: Mixing task ID is empty.
Suggestion: Please check if there is mixing or contact ZEGOCLOUD technical support to enable.
1005002Description: Mixing task ID is too long.
Possible cause: Mixing task ID is too long, maximum is 256 characters.
Suggestion: Please check if the mixing task ID is too long.
1005003Description: Mixing task ID contains illegal characters.
Possible cause: Mixing task ID contains illegal characters.
Suggestion: Please check if the mixing task ID contains illegal characters. Only supports numbers, English characters, and '~', '!', '@', '#', '$', '', '^', '&', '*', '(', ')', '_', '+', '=', '-', ';', '', ',' .
1005005Description: Mixing task configuration does not specify output.
Possible cause: Possibly outputConfig configured incorrectly.
Suggestion: Please check if outputConfig is configured correctly.
1005006Description: Mixing output target is incorrect.
Possible cause: Possibly passed illegal characters when "target" is "streamID".
Suggestion: Please check if the mixing output target is streamID type. If so, please check if illegal characters were passed. Only supports numbers, English characters, and "-", "_".
1005010Description: Start mixing task request failed.
Possible cause: Possibly due to network problems.
Suggestion: Please try switching networks and retry.
1005011Description: Stop mixing task request failed.
Possible cause: Possibly due to network reasons.
Suggestion: Please try switching networks and retry.
1005012Description: This mixing task must be stopped by the user who started the task.
Possible cause: Possibly multiple users performed mixing and stop mixing operations.
Suggestion: Please check mixing and stop mixing logic to ensure it is the same UserID operation.
1005020Description: Mixing task input stream list is empty.
Possible cause: Possibly mixing task input stream list data type does not conform to format.
Suggestion: Please check if the mixing task input stream list inputList conforms to the official website format.
1005021Description: Mixing task output list is empty.
Possible cause: Possibly mixing task output stream list data type does not conform to format.
Suggestion: Please check if the mixing task output stream list outputList conforms to the official website format.
1005023Description: Mixing task video configuration invalid.
Possible cause: Possibly mixing task video encoding format error.
Suggestion: Check if the mixing video encoding format is "h264" or "VP8".
1005025Description: Exceeded maximum input stream quantity.
Possible cause: Input stream quantity exceeded limit.
Suggestion: Please check the input stream quantity. Maximum supports 9 input streams.
1005026Description: Input stream does not exist.
Possible cause: Stream input in mixing task does not exist.
Suggestion: Please check if the streams in the mixing task input stream list inputList exist.
1005027Description: Mixing input parameter error.
Possible cause: Possibly input stream layout exceeds canvas range.
Suggestion: Please check if the input stream layout is normal.
1005028Description: Mixing input text watermark too long.
Possible cause: Mixing input parameter text watermark length exceeds limit.
Suggestion: Please ensure input text watermark length does not exceed 512 bytes.
1005030Description: Exceeded maximum output stream quantity.
Possible cause: Output stream quantity exceeded limit.
Suggestion: Please check the output stream quantity. Maximum supports 3 output streams.
1005034Description: Mixing input image link too long.
Possible cause: Mixing input parameter image link length exceeds limit.
Suggestion: Please ensure input image link length does not exceed 1024 bytes.
1005035Description: Mixing input image failed.
Possible cause: Mixing input parameter image format error.
Suggestion: Use JPG and PNG formats. Supports 2 usage methods: 1. URI: Provide the image to ZEGOCLOUD technical support for configuration. After configuration, the image URI will be provided, for example: preset-id://xxx.jpg. 2. URL: Only supports HTTP protocol.
1005036Description: Mixing input image failed.
Possible cause: Mixing input parameter image size exceeds limit or image does not exist.
Suggestion: Image size limited to within 1M or check if image path is correct.
1005050Description: Mixing authentication failed.
Possible cause: Possibly mixing configuration incorrect.
Suggestion: Check mixing configuration or contact ZEGOCLOUD technical support.
1005061Description: Failed to enable mixing.
Possible cause: Input image watermark is empty.
Suggestion: Please input correct watermark parameter [ZegoWatermark].
1005062Description: Failed to enable mixing.
Possible cause: Input image watermark parameter error, possibly layout exceeds canvas range.
Suggestion: Please input correct watermark parameter [ZegoWatermark].
1005063Description: Failed to enable mixing.
Possible cause: Input watermark URL illegal.
Suggestion: Watermark URL must start with "preset-id://" and end with ".jpg" or ".png".
1005067Description: Input background image URL illegal.
Possible cause: Input background image URL illegal.
Suggestion: Please check if the background image URL is legal. Must start with "preset-id://" and end with .jpg or .png.
1005070Description: Auto mixing server not found.
Possible cause: Possibly auto mixing server not configured.
Suggestion: Please contact ZEGOCLOUD technical support to configure.
1005099Description: Mixing internal error.
Possible cause: Possibly mixing input duplication.
Suggestion: Please check if the mixing task input stream list inputList is correct or contact ZEGOCLOUD technical support.

1006xxx/1106xxx Device Errors

Audio/video device errors may occur during Stream publishing and playing. When developers receive the deviceError device exception callback parameter "errorCode" not being 0, please handle them according to the following error codes.

Error codeDescription
1006006Description: Device unplugged.
Possible cause: Device unplugged.
Suggestion: Please check if device is in good contact.
1106007Description: Microphone loose or rapid plug/unplug causing capture exception.
Possible cause: Microphone unplugged.
Suggestion: Please check if microphone is in good contact.
1106008Description: Camera loose or rapid plug/unplug causing capture exception.
Possible cause: Camera not connected.
Suggestion: Please check if camera is in good contact.
1106009Description: Audio track capture exception stopped detected.
Possible cause: Audio capture device (such as microphone) connection exception.
Suggestion: Please check if device is connected normally. If normal, please retry or contact ZEGOCLOUD technical support.
1106010Description: Video track capture exception stopped detected.
Possible cause: Video capture device (such as camera) connection exception.
Suggestion: Please check if device is connected normally. If normal, please retry or contact ZEGOCLOUD technical support.

1009xxx/1109xxx IM Errors

Errors during IM message sending.

Error codeDescription
1009001Description: Message content is empty.
Possible cause: Message content cannot be empty.
Suggestion: Please check if message content is empty.
1009002Description: Message content is too long.
Possible cause: Message content is too long.
Suggestion: Please check if the sent message content is too long.
1009005Description: Target Room for sending message is inconsistent with currently logged in Room.
Possible cause: Target Room for sending message is inconsistent with currently logged in Room.
Suggestion: Send message passing the currently logged in Room ID.
1009010Description: Failed to send message.
Possible cause: Failed to send message.
Suggestion: Please contact ZEGOCLOUD technical support.
1009013Description: Failed to send message.
Possible cause: Message input length exceeds limit.
Suggestion: Check input content length or contact ZEGOCLOUD technical support to expand message content length.
1009015Description: Failed to send Room broadcast message.
Possible cause: QPS exceeds limit.
Suggestion: Control maximum QPS to 2.
1109001Description: Message frequency limited.
Possible cause: Message sending too frequent.
Suggestion: Please check if message sending logic is correct and reduce message sending frequency.

Error codes related to using SDK copyright music related APIs:

Error code enum valueDescription
1017000Description: command parameter invalid.
Possible cause: Input command parameter is empty.
Suggestion: Please pass the correct command parameter. See https://doc-zh.zego.im/online-ktv-android/client-api/send-extended-request#1.
1017001Description: params parameter invalid.
Possible cause: Input params parameter is empty.
Suggestion: Please pass the correct params parameter.
1017002Description: song_id parameter invalid.
Possible cause: Input song_id parameter is empty.
Suggestion: Please pass the correct song_id parameter. See https://doc-zh.zego.im/online-ktv-android/client-api/send-extended-request#1.
1017003Description: share_token parameter invalid.
Possible cause: Input share_token parameter is empty.
Suggestion: Please pass the correct share_token parameter. share_token can be obtained through song selection [requestResource].
1017004Description: resource_id parameter invalid.
Possible cause: Input resource_id parameter is empty.
Suggestion: Please pass the correct resource_id parameter. resource_id can be obtained through song selection/sharing song [requestResource] [getSharedResource].
1017005Description: start_position parameter invalid.
Possible cause: Input start_position parameter is invalid.
Suggestion: Please pass a start_position parameter with positive value, range [0, song duration].
1017006Description: position parameter invalid.
Possible cause: Input position parameter is invalid.
Suggestion: Please pass a position parameter with positive value, range [0, song duration].
1017007Description: volume parameter invalid.
Possible cause: Input Volume parameter is invalid.
Suggestion: Please pass the correct Volume parameter, range [0, 200].
1017008Description: krcToken parameter invalid.
Possible cause: Input krcToken parameter is empty.
Suggestion: Please pass the correct krcToken parameter. krcToken can be obtained through requesting accompaniment [requestAccompaniment].
1017009Description: Copyright music initialization authentication failed.
Possible cause: AppSign or Token not set.
Suggestion: When using Token authentication, call [loginRoom] before calling [initCopyrightedMusic], or use AppSign authentication.
1017010Description: Failed to request copyright service.
Possible cause: Input parameter error or network reasons.
Suggestion: Please pass the correct call parameters and retry.
1017011Description: Local disk space insufficient.
Possible cause: Local disk space insufficient.
Suggestion: Please clean up local files to ensure sufficient disk space.
1017012Description: Downloading in progress.
Possible cause: Downloading the same resource.
Suggestion: Please wait for resource download to complete.
1017013Description: Resource file lost.
Possible cause: Resource file has been deleted.
Suggestion: Please reload the resource file.
1017014Description: Expired resource file.
Possible cause: Resource file has exceeded validity period.
Suggestion: Please re-select song or request accompaniment.
1017015Description: Invalid resource file.
Possible cause: File is corrupted.
Suggestion: Please call [download] to re-download resource file.
1017018Description: Resource ID not authorized.
Possible cause: This resource ID was not obtained through [requestResource] or [getSharedResource] interface.
Suggestion: Please first call [requestResource] or [getSharedResource] interface to select song and obtain valid resource ID.
1017019Description: Copyright resource expired.
Possible cause: Copyright resource has expired.
Suggestion: Please re-select this copyright resource.
1017020Description: This resource does not support this method.
Possible cause: Resource ID passed incorrectly.
Suggestion: Please pass the correct resource ID.
1017030Description: Music has no copyright, cannot listen to and select song.
Possible cause: Music has no copyright.
Suggestion: Please select music with copyright.
1017031Description: Music has no accompaniment permission, can only listen to song, cannot select song.
Possible cause: Music has no accompaniment permission.
Suggestion: Please select music with lyrics and composition permission.
1017032Description: Not a monthly member.
Possible cause: Monthly membership not enabled.
Suggestion: Please enable user monthly membership mode or use pay-per-view mode to select songs.
1017033Description: No accompaniment resource.
Possible cause: This song has no accompaniment resource.
Suggestion: Please select a song with accompaniment resource.
1017034Description: Resource not found
Possible cause: Resource not found
Suggestion: Please select another song.
1017040Description: Illegal parameter.
Possible cause: Passed parameter is incorrect.
Suggestion: Please input the correct parameter.
1017041Description: AppID unavailable.
Possible cause: Current AppID does not support copyright music feature.
Suggestion: Please contact ZEGOCLOUD technical support.
1017042Description: Unsupported billing mode.
Possible cause: Unsupported billing mode.
Suggestion: Please select the correct billing mode.
1017043Description: Unreasonable access.
Possible cause: Monthly member pay-per-view song selection.
Suggestion: Please select the correct billing mode.
1017044Description: Share token expired.
Possible cause: Share token expired.
Suggestion: Please select an unexpired share token to obtain resource.
1017045Description: Share token illegal.
Possible cause: Share token illegal.
Suggestion: Please select the correct share token to obtain resource.
1017046Description: krcToken illegal.
Possible cause: krcToken illegal.
Suggestion: Please select the correct krcToken to obtain krc format lyrics.
1017047Description: krcToken expired.
Possible cause: krcToken expired.
Suggestion: Please select an unexpired krcToken to obtain krc format lyrics.
1017048Description: Failed to get lyrics.
Possible cause: Lyrics not found.
Suggestion: Please retry later.
1017049Description: Failed to get pitch line.
Possible cause: Pitch line not found or resource has been removed.
Suggestion: Please retry later.
1017050Description: Resource not shared in Room.
Possible cause: No user in Room has shared this resource.
Suggestion: Please have any user in the Room call [requestResource] interface to request resource and share.
1017051Description: Free acquisition times for this resource in the Room exhausted.
Possible cause: 1. Cannot re-acquire self-shared resources. 2. Already obtained shared resource.
Suggestion: Please use the already obtained resource, or use [requestResource] to re-share resource.
1017052Description: This copyright provider unavailable.
Possible cause: Copyright provider ID passed incorrectly or corresponding copyright provider not enabled.
Suggestion: Please pass the correct copyright provider ID.
1017053Description: This copyright provider does not support this method.
Possible cause: Copyright provider ID passed incorrectly.
Suggestion: Please pass the correct copyright provider ID.
1017071Description: Invalid copyright provider ID.
Possible cause: Copyright provider ID passed incorrectly.
Suggestion: Please pass the correct copyright provider ID.
1017072Description: This copyright provider does not support this songID.
Possible cause: Copyright provider music library does not have this songID.
Suggestion: Please pass the correct songID.
1017073Description: Invalid masterID.
Possible cause: When selecting Room host billing, masterID was not passed.
Suggestion: Please pass the correct masterID.
1017074Description: page parameter invalid when searching multiple copyrights.
Possible cause: When first calling multi-copyright search, page parameter must be 1.
Suggestion: Please pass the correct page value.
1017075Description: Resource has no pitch line.
Possible cause: Resource has no pitch line.
Suggestion: Please pass the correct songID.
1017076Description: Unsupported sceneID.
Possible cause: Unsupported sceneID.
Suggestion: Please pass the sceneID corresponding to the enabled scenario.
1017077Description: Unsupported topID.
Possible cause: Passed unsupported topID when getting chart songs.
Suggestion: Please pass the correct topID.
1017095Description: Copyright music module does not support this feature.
Possible cause: Copyright music module does not support this feature on the current platform.
Suggestion: Please contact ZEGOCLOUD technical support to handle.
1017096Description: Copyright music module not initialized.
Possible cause: Did not call [initCopyrightedMusic] method to initialize copyright module.
Suggestion: Please first call [initCopyrightedMusic] method.
1017097Description: System busy.
Possible cause: System busy.
Suggestion: Please retry.
1017098Description: Network exception caused failure.
Possible cause: Internal unknown error.
Suggestion: Please contact ZEGOCLOUD technical support to handle.
1017099Description: System internal exception caused failure.
Possible cause: Internal unknown error.
Suggestion: Please contact ZEGOCLOUD technical support to handle.
Error codeDescription
100001Description: Input parameter error.
Possible cause: Passed incorrect parameters or called interface incorrectly. Not thrown through player's onError callback.
Suggestion: Please check the passed interface and its corresponding parameters.
100002Description: Environment error.
Possible cause: Current environment does not support using player. Not thrown through player's onError callback.
Suggestion: Please contact ZEGOCLOUD technical support.
100003Description: Runtime failure.
Possible cause: Generally internal error caused by player itself.
Suggestion: Please contact ZEGOCLOUD technical support.
100004Description: Network error.
Possible cause: Network disconnected or network exception.
Suggestion: Check if network is normal.
100005Description: Media decoding error.
Possible cause: Media cannot be opened, unsupported media format, error during decoding cannot decode.
Suggestion: Please contact ZEGOCLOUD technical support.
100006Description: Auto play failed.
Possible cause: Due to browser auto play policy restrictions.
Suggestion: Requires user click to trigger video auto play, that is, user's click event triggers calling the player's play() method.

Previous

Upgrade Guide for Version 3.0.0 and Above

Next

Ultra-low Latency Live Streaming Pricing