At least for me, that makes no difference. Neither did using UTC timestamp. I also tried using the “Zoom Web SDK Sample Signature Node.js” for the signature creation. No luck.
Finally after a long 5 days of try I got the solution. It’s worked super for me. Excited to share my solution with you. If it doesn’t break the community guideline feel free to e-mail me arhossainim@gmail.com Because it’s a long solution I would love to send you complete code instead of describing it here.
If you are still having this issue, please email your meeting ID and Web SDK signature to developersupport@zoom.us with the error and a description of the issue and we will investigate further.
So it’s not actually about the “connection timing out” at all, it can be about four or five different security, authentication or authorisation things.
After two days of messing with it I got it working eventually, though after re-generating keys, changing versions, changing meeting id’s from numbers to strings and strings to numbers, I have no clue why.
Wouldn’t it be nice if we all lived in a world where error messages actually told you WHY something happened and helped you to correct the situation?
submitted to developersupport@zoom.com 2 days ago and still no response. I supplied all the sample code which is very basic and easy to follow, should be a 5 minute task to get an answer as to what’s wrong. I get this error {“status”:false,“errorCode”:200,“errorMessage”:“No permission”,“result”:null}
respond_to do |format|
format.json { render json: {signature: signature} }
end
end
But it works with meetings created only one account.
If i use MeetingID created another account this Error shows
“Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.”
please help me!
The solution for me was I was passing $POST['meeting_number'] and $POST['role'] into my generate_signature() function instead of $_POST['meeting_number'] and $_POST['role'] Support was able to look at my signature and determine the problem so the API should be doing this and giving better error messages.
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.
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?