Operation Scenarios

Push interruption diagnosis helps you quickly check the record of LVB push interruptions and their reasons.

Prerequisites

• You have logged in to the LVB Console.
• There is an interruption in live push under the current Tencent Cloud account.

Directions

After the LVB push is interrupted, select Auxiliary Tools > Interruption Diagnosis on the left sidebar to enter the push interruption diagnosis page.

Here:

• Path: AppName in the push address.
• Stream Name: StreamName in the push address.

The error codes and corresponding reasons are listed in the table below:

                                         Internal error in the LVB system.    The proxy layer received an interruption command.    Internal error in the LVB system.    Exception with the push linkage network.     Exception with the push linkage network.    Exception with the push linkage network.    Exception with the push linkage network.     Internal error in the LVB system.    Exception with the push linkage network.     Internal error in the LVB system.    Internal error in the LVB system.     Internal error in the LVB system.     Internal error in the LVB system.    Internal error in the LVB system.    Failed to get the customer information corresponding to the push link.    Your LVB service has been disabled.     You LVB service has been temporarily disabled due to arrears of your account. Please top up promptly.    Your LVB service has been forcibly disabled.    Push with an IP address is not allowed.    Unable to identify the push domain name.    The push domain name is invalid.    The push domain name is disabled.    The push application name is disabled.    The pushed stream name is in forbidden status.    The access mode is channel mode, but the corresponding push channel has not been created yet.    The access mode is channel mode, but the current push channel has been disabled.    The pushed stream name contains invalid characters.    The push application name contains invalid characters.     The push client IP is in the blocklist.    The push client IP is not in the allowlist.     The push does not carry the expiration time parameter.    The parameter value of the expiration time has expired.     The push does not carry the authentication parameter.     Authentication parameter verification failed.     The current number of pushes exceeds the maximum value allowed by the configuration.    The number of pushes corresponding to the current stream name exceeds the maximum value allowed by the configuration.    Third-party authentication failed.    The system actively disconnected the push as there was no data for a prolonged time.    A push interruption request from the client was received.    A playback forbidding request from the client was received.    A new push link was received to replace the current push.     Unknown reason.    Exception with the RTMP protocol content.    Internal error in the LVB system.    Unknown reason.    Unknown reason.    Unknown reason.     Unknown reason.    Unknown reason.     Unknown reason.    Unknown reason.    Unknown reason.     Exception with the RTMP AMF data.    Unknown reason.    The push client actively stopped the push.  

Error Code		Reason
0		Unknown error.
1		The push client actively stopped the push.
2		The push client actively stopped the push.
3		The push client actively stopped the push.
4		The push client actively stopped the push.
5		Internal error in the LVB system.
6		Exception with the RTMP protocol content.
7		The size of a single RTMP frame exceeds the maximum value allowed by the configuration.
8		The system actively disconnected the push as there was no data for a prolonged time.
9
10
11
12
13
14
15
16
17
18	100
	101
	102
	103
	104
	200
	201
	202
	203
	300
	301
	302
	303
	304
	305
	306
	307
	308
	309
	400
	401
	500
	501
	502
	503
	600
	601
19
20
21	100
	101
	102
22
23
24
25
26
27
28
29
30
31
32
33
34
35

LVB also provides an API for querying errors.