Hey @samadhan.madane31,
The only requirement is a Pro or higher account to host the meetings. You do not need to pay to join meetings with the Web SDK.
Thanks,
Tommy
Hey @samadhan.madane31,
The only requirement is a Pro or higher account to host the meetings. You do not need to pay to join meetings with the Web SDK.
Thanks,
Tommy
SDK web was working fine until last night
Today it returns to me “Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.”
@tommy check, please this issue
SDK web was working fine until last night
Today it returns to me “Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.”
Can you please ensure you’re on the latest version of the web SDK (1.8.0), as well as confirm the following:
The error you’re seeing usually stems from one of the factors mentioned above.
Thanks!
Will
Currently use version web SDK (1.8.0)
I also use an account PRO
Unfortunately I got a problem
“Joining meeting timeout.
The signature has expired.”
This is the request sent
name=
&mn=
&email=
&pwd=72205311
&role=0
&lang=en-US
&signature=
Hey @ahmed,
Make sure you create the signature right before you join the meeting.
Let me know if this thread helps:
Thanks,
Tommy
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
Hey @ahmed,
Your signature looks correct!
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
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();
},
});
@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
Any Update regards our issue
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
add ```
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.
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
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”
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
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