Start from a secure page

Camera access normally requires HTTPS or a local development context. Open Rapid Cactus from its secure address, then select Start monitoring or Start webcam test. The site does not request camera access before that action and never requests audio.

When the browser asks

Choose Allow only if you want this browser tab to use a camera. If you block or dismiss the request, no preview can begin. You can review the browser’s permission for this site and try again, but browser controls and labels change over time, so use your browser’s current help rather than following old universal menu paths.

If access is blocked or unavailable

  • Permission blocked: review the camera permission for this site in your browser, then return and select Start again.
  • Camera busy: close another app or browser tab that may be using the camera, then retry.
  • No camera detected: connect, uncover, or enable a camera and wait for the operating system to recognize it.
  • Camera disconnected: reconnect it, then stop and start a fresh local session.
  • Preview does not start: check that the page is secure, refresh it, and use the Webcam Test to separate a permission problem from a monitoring setup problem.

Camera names and switching

Browsers often hide camera labels until permission is granted. After a preview starts, available cameras may appear in the camera selector. Mobile browsers can limit switching, especially while another app has the camera; stopping the session and starting again is a safe fallback.

Private browsing and mobile limits

Private or incognito windows can apply different permission and storage rules. Mobile browsers may pause camera work when the page is hidden, the device locks, or another app opens. Keep the page open and the device awake while testing or monitoring.

Keep device security in place

Rapid Cactus cannot override a browser or operating-system denial. Do not weaken operating-system security to make a preview work. Resolve the current browser permission, camera connection, or competing-app issue instead.