You may notice some articles displaying content inconsistently. Pardon our dust as we update our site.
cross icon
Error: 'Incorrect Meeting Password'

ISSUE
Users encounter an 'Incorrect Meeting Password' error when attempting to join a Webex meeting. This error prevents access to the meeting, causing delays and disruptions.

Important Note
If you need the password for your meeting or have yet to receive an email invitation, you can contact your meeting host for help. For assistance, please see WBX71898—How Do I Contact the Host of My Meeting

Webex Technical Support cannot access meeting passwords, provide password assistance, or resend meeting invitations.

RESOLUTION

To resolve meeting password issues:

If you are manually entering the password:  
  • Enter the password EXACTLY as shown in your email invitation. The password may include periods or special characters at the beginning or end.
  • Check the Caps Lock and Num Lock keys on your keyboard. Passwords are case-sensitive, and these settings will alter the passwords you enter.
  • Be sure that you are not typing in an "I" or an "L" instead of a number "1".  Depending on the font in the notification email, these characters may all look alike, but the logic behind each character is very different. This will cause errors in your password entry.
  • If you are unsure, copy and paste the password from the invitation email.

If you copy and paste the password from the invitation email:

  • Make sure you select the entire password and do not select any extra characters or spaces.
  • You can copy and paste into Notepad to verify you have the correct text.

If none of the above works:

  • Contact the meeting host for the password.
Note: The host may have changed the password or altered the meeting without sending you an update notification.  After you have completed your troubleshooting steps, contact the meeting host.  CAUSE
Possible causes for the 'Incorrect Meeting Password' error include:
  1. The password needed to be typed correctly.
  2. An incorrect password was sent to you by the host.
  3. Invalid data in your web browser cache.
  4. A technical issue interferes with your meeting access (though this is less likely).

Was this article helpful?