Open the HTTPS site directly
Visit https://omeglehang.com/ in your browser. Camera capture normally requires a secure context. Embedded browsers and hosting preview frames can restrict devices even when the main site allows them.
Confirm the 18+ and rules statement, then click Video Chat. Text Chat does not request devices. Unmonitored asks for a separate warning agreement before it requests camera and microphone access.
No prompt does not necessarily mean no request
Your browser can remember that you already allowed or blocked a site. With an allowance, the local preview may start immediately. With a block, capture can fail without showing a new prompt.
Open the browser's site information or site controls beside the address bar. Look for Camera and Microphone permissions. Menu wording varies by browser and version. Set an appropriate permission, reload the site, and start video again. The site cannot reset or force a browser permission prompt.
Check operating-system privacy and other apps
If the browser has permission but cannot open a device, check the operating system's camera and microphone privacy settings. Ensure the browser is allowed to use them. Close another video-call, recording, or camera app that may have exclusive access.
Test the webcam and microphone in a trusted local app. If they fail there too, the issue is likely device, driver, connection, or system configuration. Repeatedly changing a website setting will not create missing hardware.
Read the displayed failure
- Access blocked: browser or system permission was refused.
- No available camera: the browser could not find a working camera.
- Device error: a device exists but could not start, possibly because another app is using it.
- Hosting policy: a server header or embedding frame prevents device access.
- Unsupported browser: the page cannot use the required media API in that browser or context.
The chat stays open with an appropriate retry control rather than automatically returning home. Stop cancels the session; it also releases a late device response so capture should not remain active after you leave.
The preview works, but the stranger does not connect
This is a different stage. A working preview proves local capture; it does not prove that two browsers can establish a network path. WebRTC connectivity checks may fail on restrictive networks even when both people have devices.
Try a stable connection and an updated browser, and note the visible connection status. Do not install a stranger's suggested software or disable broad security protections. The site operator may need to investigate signaling, proxy configuration, and relay infrastructure.
What to include in a useful problem report
Use Contact with the browser name, device type, the displayed error, whether a local preview appeared, and approximately when it happened. Do not include passwords, verification codes, another person's private messages, or explicit media.
Use text chat if you want to continue without devices. Read the start guide for the normal flow and Safety before returning to video.