Video Encoder Faults: Login Failures, Blank VLC and a Broken Picture

Start here: the interrupt counter

A large share of "the encoder is broken" reports are resolved by reading this number. Record it before raising a ticket.

Fault 1: cannot log in

1. Is the IP correct: confirm the address you are browsing matches the device's actual address.
2. Are both LEDs lit: power and network/status.
3. Is the network connection sound: cable seated, switch port healthy.
4. Direct connection caveat: when a PC is connected straight to the encoder, the PC must be given a manual IP — there is no DHCP server to obtain one from. This is the single most common cause of "cannot log in".

Fault 2: forgotten IP address

The unit has an RST button or hole for factory reset:

1. With power applied, hold it for about 10 seconds;
2. Release once the status LED goes out;
3. The unit restarts automatically with all parameters back to factory defaults.

Log in again at the default address. Be aware: a reset clears all custom configuration (IP, bitrate, publish URLs and so on). If the unit is live, record the current settings first.

Fault 3: only the power LED is on

1. Confirm the encoder is properly connected to the network or PC.
2. Use ping to check whether the encoder responds.
3. Reachable but the web page will not load → contact technical support.
4. Not reachable and the IP is unknown → perform the reset above.

Fault 4: VLC shows no picture

This is the fastest way to verify an encoder. The standard procedure:

1. Install the latest VLC (older builds have protocol gaps).
2. Log in to the encoder, find the access URL under Status, and copy it.
3. In VLC: Media → Open Network Stream, paste the URL.

If there is still no picture, go back to the counter. Zero interrupts means no input — check source and cabling. A rising counter with no VLC picture means check that the access URL is right and that VLC is current.

Fault 5: macroblocking and flicker

1. Confirm VLC is the latest version — rule this out first.
2. Open Status → Hardware Status → Interrupt Count.
3. If lost interrupts exceed 2 and the number keeps changing on refresh, there is probably a signal incompatibility; test with a different source.

Such faults usually trace to the format or quality of the incoming signal rather than the encoder. Cross-testing with a known-good source is the fastest way to settle it.

Fault 6: publishing but nothing on the platform

Likely cause	How to check
Codec mismatch	Use H.264 for RTMP; H.265 is rejected by many platforms, showing as black video or audio only
DNS not configured	Required when publishing to a domain; symptom is "network fine, nothing goes out"
Wrong URL hierarchy	Application name and stream key are platform-assigned; wrong values connect but fail to publish
Bitrate above upstream capacity	Set bitrate at 60–70% of measured upstream and leave headroom
Outbound port blocked	Confirm 1935 (RTMP) or 443 (RTMPS) is allowed out

Order of investigation: local first, network second

The first three steps are entirely within your control and take minutes. Only when all three are clean is it worth chasing the platform and the link.

For telephone support call +86 513 8358 6411. When you contact us, include: model, firmware version, the measured interrupt count and the access URL — that alone removes most round trips.