Proxy Settings and Separate CaptureGem Profiles
CaptureGem’s proxy controls are intended for the app’s supported browser and recording workflow. They do not create a remote web dashboard or a separate recording service for each site.
The desktop app does not provide documented --port and --config-dir customer flags for running multiple Windows instances. A reverse proxy configuration that assumes those flags and exposes local recorder ports can fail or expose private controls.
If you are testing another profile, use an isolated CAPTUREGEM_DATA_DIR environment override and confirm the resolved path in the app logs. Keep different profiles’ configuration and temporary media separate. Do not run overlapping recordings against the same output folder without checking the resulting files. For ordinary use, one CaptureGem instance with separate model entries is the supported starting point. See file locations and proxy guidance.
Loading comments...