Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again

Hey @cinemed, @jesusaugusto.008,

Happy to hear you figured out the issue. Yes, one of our top priorities is adding more specific error messaging. :slight_smile:

Thanks,
Tommy

Hey @mikko.valjento, @jwiebe,

Sorry to hear you are having trouble with the Zoom Web SDK and have decided to look for alternatives. One of our top priorities is adding more specific error messaging.

Apologies for the inconvenience,
Tommy

Hey @aokirihito,

Like @penar.musaraj, is saying, you can only start meetings that are owned by the same Zoom account that owns the JWT App.

You can join any meeting regardless of who owns the JWT App.

Thanks,
Tommy

still get same message “Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.” any updates ?

Hi Folks, I am also getting this message today, I checked the status page : https://status.zoom.us/ and everything indicated as operational including Zoom Developer Platform - Web SDK. Is there are known issue at the moment?

Just a quick Update - Mine is Working Fine if the Meeting is a “Meeting” but does not work if the Meeting is a Webinar. So anyone know if this is working for webinars.

OK, I found my issue with Webinars. Ensure to set the email address when joining the webinar, and ensure that this email address is NOT the host’s email address e.g.

ZoomMtg.join({
        meetingNumber: meetConfig.meetingNumber,
        userName: meetConfig.userName,
        userEmail: meetConfig.userEmail, //required for webinars and not be the HOSTS email address
        signature: res.result,
        apiKey: meetConfig.apiKey,
        passWord: meetConfig.passWord,
1 Like

do you have an updated version of this?

I can confirm this was our problem. The developer account needs to be pro for the SDK to work with meetings creating by other accounts, otherwise you get this error.

Hey @darragh.duffy, @miked,

Happy to hear you figured out the issue! :slight_smile:

Thanks for sharing your solution!

-Tommy

Hey @a7med.3bdelnasser22, @Evanatzend,

Please check the two possible solutions mentioned above by @miked and @darragh.duffy.

Let me know if that helps! :slight_smile:

Thanks,
Tommy

We too have the dreaded “Your connection timed out” error, but, on one specific machine…

We can succesfully start a meeting and have people join through web, on all other machines

Our specifics are:

  • We use SDK 1.7.8
  • Developer account is not pro
  • Developer API key/secret is not host account
  • Meeting starter account is not pro

(So all those things don’t seem to be causing it)

The machine that we can’t succesfully start a meeting with, has the latest zoom client installed, meeting-id and password are correct, no firewalls known, time is synced. Works client to client.

What are we missing?

1 Like

Hey @joep,

What type of machine, OS version, and browser?

Thanks,
Tommy

I am getting this below error msg from all browser.

Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.

Hi Tommy,

Thank you for reaching out. I will get back to you with the specifics asap.

Best,

Joep

Hi Tommy,

This is what I know about the machine that we can’t connect to using the web SDK.

(As for the browser version: we use this machine to start a zoom meeting from the Zoom application, so there’s no browser involved)

image

Hey @tutorops24,

Please create a new topic if the solution did not work for you.

Thanks,
Tommy

Hey @joep,

Thanks for sharing the computer info. What browser are you using though?

The developer account who created the JWT App does need to be pro.

Thanks,
Tommy

Hi @tommy, thank you again for your response.

What browser are you using though?

Chrome, on Win10, both latest.

The developer account who created the JWT App does need to be pro

But that implies that it shouldn’t work at all, where in fact, it works everywhere except on the one single mac. How is that possible?

Best,

Joep

Hey @joep,

Thanks for the clarification! Can you make sure the Mac’s time settings are synced properly:

Thanks,
Tommy