Reolink RTSP works but ONVIF fails: what to check

RTSP and ONVIF have separate settings

Reolink documents per-protocol server switches on supported cameras; some ports are disabled by default and some models do not expose a switch. Its Synology guide shows ONVIF authentication on default port 8000, while its general troubleshooting checks IP, port, credentials, local network, firmware and login lockout. A valid RTSP URL cannot certify ONVIF discovery or event support.

What not to infer from the RTSP test

RTSP addresses streaming media. ONVIF discovery and control use another service configuration. When only RTSP succeeds, record both endpoint settings and the error shown by the client; do not assume a codec fault or an unsupported camera without further evidence.

Check your setup

1. Identify the exact model and confirm ONVIF support in Reolink’s product/protocol list before changing any port.
2. In Reolink App/Client server settings, verify ONVIF is enabled when the model offers that control; if attached to an NVR, inspect the NVR port settings instead.
3. In Synology or another client, use the camera’s actual ONVIF port (8000 is Reolink’s default in its Synology example), IP and account credentials; check LAN reachability and login lockout.
4. If ONVIF authenticates but a particular feature still fails, test that feature independently under the exact integration profile. Video alone is not a FULL compatibility verdict.

What this does not establish

Default port numbers and protocol toggles can vary by model or user configuration. This troubleshooting flow makes no model-specific ONVIF feature claim.