Skip to content

article

Troubleshooting Common StretchMeet Issues

Fix the most common StretchMeet problems — join errors, passcode failures, camera/mic issues, and meetings that won't start.

Most StretchMeet issues fall into a handful of categories. This guide walks through the common ones and how to resolve them quickly.

Can't join a meeting

"Meeting room was not found."
The link is incorrect or the meeting was deleted. Ask the host to re-share the current join link, and check you copied the whole URL.

"Meeting room is not joinable."
The room is cancelled, ended, or archived — none of these can be joined. The host needs to create a new meeting.

Stuck in the waiting room.
With host approval on, a host or co-host must admit you. Message the host if no one lets you in. Hosts: watch the waiting list and click Admit.

"Too many join attempts."
Public guest joins are rate-limited to protect the room from abuse (roughly 20 attempts per room per minute). Wait about a minute, then try again with the correct passcode.

Passcode problems

"The meeting passcode is invalid."
The code entered doesn't match. Passcodes must match exactly. Re-share the current passcode and try again.

"This room requires a passcode, but no guest passcode is configured."
The room is set to require a passcode but none was actually set. The host should edit the room and add a passcode, or turn off passcode required.

Camera and microphone

Camera or mic won't turn on.
1. Check the browser's site permissions and allow camera + microphone for StretchMeet.

2. Make sure no other app is holding the camera (close other video tools).

3. Reload the meeting tab after granting access.

4. Confirm the right device is selected in your browser/OS settings.

Others can't hear me.
Check you're not muted (by yourself or by the host), that the correct microphone is selected, and that your OS input volume is up.

The meeting won't start

"Only a host can start the meeting."
Starting requires a host or co-host role. Confirm your role, or ask the host to start it.

The room won't go live.
Confirm the room isn't already cancelled or ended, and that the selected provider is available. Native meetings need the StretchMeet engine to be ready; external-provider meetings need that provider to show connected, not needs auth or disabled.

Recording or intelligence missing

Recording won't start.
Recording runs on the native engine and requires the meeting to be live, plus a host/co-host role. Confirm the room uses StretchMeet (native).

No transcript or summary.
These are produced when transcription/recording is enabled. If transcription mode was off and nothing was recorded, there's nothing to transcribe or summarize. Enable them for next time. If they're still processing, wait and refresh. See Transcripts, AI Summaries & Artifacts.

Poor call quality

If video freezes or audio breaks up, open the Quality view. If only one participant is affected, it's their network — suggest wired ethernet, disabling VPN, and closing other bandwidth-heavy apps. If everyone is affected, check the engine status. See Monitoring Meeting Quality and Connection Health.

A realistic example

A guest reports they can't get into a client call. The host checks and sees the room requires a passcode, but the guest keeps getting "invalid passcode." The host realizes they sent last week's code. They re-share the current passcode; the guest tries again but now sees "too many join attempts" because of repeated tries. After waiting a minute, the guest enters the correct code, lands in the waiting room, and the host admits them. Total fix time: two minutes.

Tips

  • Reload first. A quick tab refresh clears a surprising number of camera/mic and connection glitches.
  • Verify role before troubleshooting host actions. Many "it won't let me" issues are simply a missing host/co-host role.
  • Re-share fresh links and codes. Old links expire and old passcodes may have changed.
  • Test alone before big calls. Catch device issues before an audience is watching.

When to get more help

If a problem persists after these steps — especially if everyone on multiple meetings is affected — it may be a platform-level issue. Note the exact error message and the meeting involved, and contact your StretchSuite administrator or support.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.