Step-by-step support · Camera connections

Push video from a camera, Raspberry Pi or encoder

Publish outward with a dedicated credential instead of opening your camera network.

Create the camera

In the app choose Add Camera → secure publishing. Enter a recognizable name. Creation keeps recording off. If the server says push ingest is unavailable, use a direct source or the LAN gateway until the operator enables it.

Save the one-time connection details

Save the generated URL privately. RTMPS uses TLS on TCP1936; RTSPS uses TLS on TCP8322. SRT uses UDP8890 with both publisher authentication and its separate encryption passphrase. Never paste real publish URLs into support tickets or analytics. Credentials expire after one year and are revoked by account sign-in security changes.

Configure the sender

OBS or a camera with RTMPS publishing can use the generated RTMPS URL. For Raspberry Pi or FFmpeg, select a real camera input and publish H.264 video with a keyframe interval of at most two seconds; AAC audio is optional. RTSP publishing requires ANNOUNCE/RECORD support, not just RTSP viewing. Keep TLS certificate verification enabled. SRT must send MPEG-TS as a caller and include the exact StreamID and passphrase.

Verify private output and recording

Check the publisher observation in the app, open camera live view and confirm actual video. Review masks/audio and recording access before starting recording. Wait for confirmed footage, then play the timeline and export a short clip. A connected publisher alone is not proof of a decoded or saved recording.

Rotate or revoke when needed

Stop an unwanted feed by revoking its publisher. Rotation replaces the URL/key and disconnects the prior feed; update the sending device afterward. Saved footage is retained. An encoder must reconnect after internet or service interruptions. CamBackup cannot recover frames that never reached it.

What success looks like

A private incoming camera produces live output and, when entitled and enabled, new timeline footage through ordinary CamBackup workers.

If it does not work

Plain RTMP/RTSP are not exposed publicly. WebRTC/WHIP, raw UDP/RTP and HLS file-upload publishing are not enabled in this version. Use the outbound LAN gateway for unsupported publishing devices. Do not disable authentication or TLS to work around a device limitation.

Still stuck?

Contact CamBackup support with safe error text, time/timezone and the steps tried. Never send passwords, tokens, OTPs, recovery codes or credential-bearing camera addresses.

Related guides

Reviewed 17 October 2026 · English