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

Meeting SDK Web
233

Hi tommy
Thank you very much for your response
I have been suffering from zoom problems for the past 17 days
Was working fine 1.7.7 but it stopped working
Then came the virgin 1.8.0, but it also does not work
Then I did the last thing you advised me, and the problem still exists
This caused me many problems with clients
These are some things that may help you solve my problem
my request

and this response
on screenshot
zoom

234

Hey @ahmed,

Your signature looks correct! :slight_smile:

Can you share the code you are using to generate it? You can reference the Web SDK sample code for generating a signature. We did update the expiration time around the same time as we released version 1.7.7.

Thanks,
Tommy

235

Hi tommy
I am already using Web SDK sample code for generating a signature

itā€™s code
var signature = ZoomMtg.generateSignature({
meetingNumber: meetingConfig.mn,
apiKey: API_KEY,
apiSecret: API_SECRET,
role: 1,
// role: meetingConfig.role,
success: function (res) {
console.log(res.result);
meetingConfig.signature = res.result;
meetingConfig.apiKey = API_KEY;
var joinUrl =
testTool.getCurrentDomain() +
ā€œ/meeting?ā€ +
testTool.serialize(meetingConfig);
$(element).attr(ā€œlinkā€, joinUrl);
var temp = ("");
$(ā€œbodyā€).append($temp);
temp.val((element).attr(ā€œlinkā€)).select();
document.execCommand(ā€œcopyā€);
$temp.remove();
},
});

236

@tommy
Unfortunately Tommy, the issue is the same , although you reply me that the signature looks correct , kindly support us , whereā€™s the problem. How we can solve it if itā€™s from our side
Regards and waiting your reply asap

237

Any Update regards our issue

238

Hey @ahmed,

Can you please provide a sample github repo so I can debug the issue locally?

I am unable to reproduce this on my end.

Thanks,
Tommy

239

add ```

240

Hey @Real_Intel,

Let us know if you have any questions we can help with!

Best,
Will

241

I am seeing this issue with v1.8.5 when the meeting has not started. With v1.8.3 I would get a more accurate error alert saying that the meeting has not started yet. With v1.8.5 Im getting this connection error. Then when I start the meeting, and retry sdk implementation, the error goes away and I can join the meeting no problem.

If this connection time out error is being caused by meetings not being started, it would be nice to revert to the old error message which was more accurate.

242

Hey @kurt2,

Thank you for reaching out to the Zoom Developer Forum. Do you see this same issue when using the latest version of the Web SDK (v1.8.6)? When I test on that version I see a more accurate error message when the meeting hasnā€™t started.

Thanks,
Max

243

yes, i am seeing the same issue with Web SDK v1.8.6 and its not giving a good user experience. it should say that ā€œMeeting hasnā€™t started. Please wait for host to joinā€

244

Hey @dilipksah ,

We are aware of this issue and working on a fix in a future version.

Thanks,
Tommy

245

Currently use version web SDK (1.8.0)
Unfortunately I got a problem is a very strange problem
ā€œJoining meeting timeout.
The signature has expired.
But when you reload the page, maybe many times
it might work
I do not know the reason for that

246

Hey @ahmed,

The next time you encounter this, can you share your signature with us here, as well as a screenshot of the browser console? This will help us to take a closer look.

Thanks!
Will

247

Hey Will

I am already using Web SDK sample code for generating a signature

itā€™s code
var signature = ZoomMtg.generateSignature({
meetingNumber: meetingConfig.mn,
apiKey: API_KEY,
apiSecret: API_SECRET,
role: 1,
// role: meetingConfig.role,
success: function (res) {
console.log(res.result);
meetingConfig.signature = res.result;
meetingConfig.apiKey = API_KEY;
var joinUrl =
testTool.getCurrentDomain() +
ā€œ/meeting?ā€ +
testTool.serialize(meetingConfig);
(element).attr(ā€œlinkā€, joinUrl); var temp = (""); (ā€œbodyā€).append($temp);
temp.val((element).attr(ā€œlinkā€)).select();
document.execCommand(ā€œcopyā€);
$temp.remove();
},
});
ā€¦
screenshot
screenPNG

when reload page many of time might work
screen when its work

screen2
screen21014Ɨ601 21.1 KB

248

Hi @ahmed,

Can you double check your time settings on your server?

Please also ensure that your signature expiration is still valid when you start the meeting.

Thanks,
Will

249

HI Will
The time on the server works fine
Can I understand why it might work once and again not
From where do I know what the problem is because it is very strange
We are in big trouble because of this point

250

Hi, Iā€™m getting this error when using the react sample app. Itā€™s using SDK v1.9.0. Iā€™ve followed the setup instructions, with the only change being to rename app.js to App.js because the file was incorrectly named out of the box.

  • Iā€™m using a JWT App type for the key (though thereā€™s nowhere in the setup that asks for the secretā€¦)
  • My developer account is Pro
  • Iā€™ve tried both starting a new meeting (with role == 1) and joining an existing meeting (with role == 0) with the same error both times
  • There is no issue with signature generation - my endpoint is live and Iā€™m able to successfully retrieve signatures with Postman

Any ideas on what the issue is or where to look? Other details are that Iā€™m on OS Catalina 10.15.1 and Iā€™ve tried both Brave Browser 1.18.77 (shields down) and Safari 13.0.3. Thanks.

251

Hey @keaton ,

Did you add your JWT Secret to your signature generation server? :slight_smile:

If you continue to see issues, please create a new topic and fill out the post template so we have enough info to help.

Thanks,
Tommy

252

Hey @ahmed ,

You need to generate the signature on the server side in UTC time. Checkout this working example:

Thanks,
Tommy