Connect a camera

Special characters in RTSP credentials

The short answer

Prefer separate credential fields. If credentials must be embedded in a URL, encode only those components so reserved characters do not become URL delimiters.

Reference 1

Work through the checks

  1. Use the camera’s local protocol account. A cloud app email address is not necessarily a valid RTSP or ONVIF login. Grant only the viewing or control permissions actually needed.

  2. Enter credentials in separate app fields when available. For a URL that must contain credentials, encode reserved characters only in the user/password components; never encode the complete RTSP URL.

  3. Stop repeated failed logins and check the camera’s account lockout policy. Verify the local account in the manufacturer interface before trying again with one client.

  4. Before sharing a URL, screenshot or log, remove passwords, tokens, public addresses and identifying camera names. Share the error time, app version and sanitized stream format instead.

Example to adapt
rtsp://<encoded-user>:<encoded-password>@192.0.2.10:554/<path>

What to verify

Test one camera and one stream before opening a larger camera wall. Keep the camera settings unchanged while you establish whether the first live image is stable.

Sources and scope

AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.

Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.