Direct answer
RTSP 404 usually means the server is reachable but the requested media resource is not present at that path. Keep the host and port fixed, then verify the vendor path, channel number and main/substream suffix.
Why this happens
Camera families often use different paths for direct cameras, NVR channels, dual lenses and substreams. A copied example can therefore reach the correct server while asking for a resource that the installed model does not expose.
Start from the exact status code or network symptom, then change one layer at a time.
A controlled test
Begin with the manufacturer’s current manual for the exact model and firmware. Test one path at a time and do not change the IP address, account and transport in the same attempt.
Change one variable at a time. Keep the camera model, firmware, endpoint and account recorded; then test network reachability, protocol response, media transport and decoding as separate layers.
Use a dedicated view-only account and a trusted local diagnostic tool. Redact credentials, private addresses and identifying data before sharing output.
Diagnostic sequence
| Check | Action | Evidence of progress |
|---|---|---|
| Endpoint | Confirm the response comes from the intended camera or recorder. | The server identity and IP match the installed device. |
| Path | Compare every slash, channel and subtype with official documentation. | DESCRIBE returns a media description instead of 404. |
| Recorder | When using an NVR, address the NVR and the assigned channel. | The selected channel maps to the expected camera. |
| Stream | Try the documented substream only after the main path is known. | Both profiles are identifiable rather than guessed. |
Evidence to keep
A successful DESCRIBE response is stronger evidence than a ping or open port because it proves that the requested media resource exists.
Boundary and safety note
Do not publish a vendor URL table as universal truth; model, recorder mapping and firmware can change the path.
For remote viewing, use a managed VPN instead of exposing RTSP or camera administration ports directly to the public internet.
SmartRTSP
SmartRTSP is a camera-focused RTSP and ONVIF viewer for Apple devices, Windows and Android. It fits direct viewing, discovery and multi-camera checks; keep a dedicated NVR or VMS when continuous recording, evidence export or centralized enterprise controls are required.
Frequently asked questions
Is RTSP 404 a password error?
Normally no; authentication failures use a different response such as 401.
Can the port be correct while the path is wrong?
Yes. The RTSP service can answer on the right port and still report that a media resource does not exist.
Why does the direct-camera URL fail through an NVR?
The recorder usually exposes its own channel-addressing scheme rather than forwarding the direct-camera path unchanged.
Primary references
- IETF RFC 7826 — Real-Time Streaming Protocol 2.0
- SmartRTSP — official platform and product information
Related SmartRTSP guide
Open related guideUse the RTSP response to distinguish a reachable camera with a wrong resource path from a network or password failure.