Troubleshooting

Find the first failing step: Rerinku View service → camera connection → live video → recording → AI or remote access. Reproduce with one camera on the LAN first, then compare other devices and external access.

Console unavailable or startup fails

1. Run curl http://127.0.0.1:8080/healthz on the Rerinku View host, using your actual address and port if changed. A healthy service returns 200 and {"status":"ok"}. This checks the service and database, not camera health.
2. If local access fails too, read startup logs. Check occupied ports, unknown configuration keys and write permissions on config, data and component directories. A file specified with RERINKU_CONFIG must already exist.
3. If only another machine fails, check whether the listener is restricted to 127.0.0.1, then check the firewall and container network. Use the host’s LAN IP from another machine, not localhost.

Environment variables override files, which override defaults. Paths resolve against the working directory. See the Configuration reference.

Camera not discovered or cannot be added

Symptom	Check first	Verify the fix
Empty ONVIF discovery	Same subnet, ONVIF enabled, multicast, UDP 3702 and Docker Desktop network limits	Try adding manually by IP
Credentials rejected	Camera username, password and ONVIF permissions, rather than Cloud credentials	Adding passes the connection check
RTSP URL rejected	Embedded username or password	Move credentials to separate fields and add again
No GB28181 channels	SIP parameters, password, port 5060 conflicts and listener status in settings	Registered channels appear in discovery
USB missing or busy	Linux, output format, video group, container device mapping and other programs using it	Release the device and check again; YUYV/NV12-only devices are unsupported

For full protocol instructions, see Connecting cameras.

Live video does not play

1. Read the player message. Incorrect credentials, missing streams and unsupported codecs need their corresponding settings corrected. If H.265 fails, test an H.264 stream. See Streams and codecs.
2. Compare LAN and external access. The console and live media use different connections. A working page only proves HTTP connectivity. If video works locally but not externally, check WebRTC ICE, UDP or TURN paths in Configuration and Remote access.
3. Play one camera first. Enable the player’s debug HUD and inspect frame rate, bitrate and packet loss. MJPEG transcoding and AI decoding use resources. Confirm continuous playback before adding panes.

The player retries network failures automatically; you can also select Retry now. See Disconnects and reconnecting.

Recordings missing or playback empty

1. Confirm continuous recording is enabled for the device. Live video alone does not mean it is recording.
2. Select the correct device, stream and date. The calendar uses your browser’s time zone; file directories use UTC dates.
3. Check free disk space, capacity, retention days and directory write permissions. recordings paused to protect storage means storage protection paused recording; it resumes when space is available.
4. If an event has no video, check for footage at that time and whether the device supports event recording. SDK devices and Rerinku Cam need continuous recording enabled.

See Recording and playback. Remote uploads begin after local files are finalized.

AI unavailable or resource use high

Check Supported platforms, model downloads and the camera’s object-detection switch. Face recognition also needs the person category and a face library.

Check performance under Settings → AI detection, and per-stream hardware decoding under Settings → Video decoding. GPU decoding and GPU inference have separate platform support. Reduce detection cameras or use a lower-resolution detection stream, then compare load. See AI recognition for models, frame rates and acceleration.

Quick Connect or phone notifications fail

• Confirm Rerinku View works on the LAN first. A node revoked in Cloud must be disconnected and removed in Rerinku View before connecting again.
• For external phone access, check the saved server address. Pairing QR codes omit the Quick Connect address, and the app does not switch automatically between LAN and public addresses.
• A new phone cannot bind to password-protected Rerinku View in the current app; existing bindings continue to work.
• Send a test from Settings → Notifications → Phone push. Check system notification permission, device and category filters, and Rerinku View’s outbound connectivity. If text arrives without an image, also check that the phone can reach Rerinku View.

See Remote access and the phone app and Events and notifications.

Collect diagnostic information

Record the Rerinku View version, OS and architecture, native or Docker installation, camera protocol and codec, failure time and time zone, whether LAN and external access both fail, and nearby logs and player messages.

For the Linux service name used in this guide, run journalctl -u rerinku-view -n 100 --no-pager. For Compose, use docker compose logs --tail=100. Save terminal output for manual runs. See Logs. Remove passwords, tokens, QR codes, public node addresses and face photos before sharing.