ZoomMtg.join() returns "The signature has expired."

Meeting SDK Web
21

Hey @r.abdelhamed,

Please see my reply to your post here:

Please also refrain from double posting.

Thanks,
Tommy

22

Dears,

Thanks alot it solved

I used your signature example app and it is worked

1 Like
23

Happy to hear you got it working! :slight_smile:

Thanks,
Tommy

24

Hello Tommy,

We are facing same problem in windows 10 os can you please provide the signature example app to us.

Thank You…

25

Hey @kumkumschool,

Here are instructions to generate the signature, and the sample app:

Thanks,
Tommy

26

Hello guys
I’m having the same issue here, generating the signature using the websdk or manually implementing the code mentioned here. I don’t see a solution on the web, I noticed that most of the times the error just goes away for the ones who had the problem without implementing any solution.

any advice ?

27

Hi @ramy.dridi

Most of the times the issue is because the laptop date and time settings are not correct. Either the time is not correct or timezone is not correct. Once you rectify this and set the time to auto sync, this should get resolved.

28

Hello @helloparent , Thank you for replying!
so I read that generating the signature on the server might fix the problem. however, fixing the date/timezone of the server means that I should set the right timezone for it depending on its place? is that it?
thank you again!

29

For us setting the timezone of the computer/laptop on which the SDK is running right solved the issue.

30

I guess that’s not practical for my case. the app will be used by hundreds each day and fix the date/timezone is a bit handy for me of users (yeah, believe me)

anyway, thanks for your input, I’ll try the backend solution and will leave the solution here if it works, thank you again!

31

Hey @ramy.dridi,

Were you able to get it working?

Thanks for your input @helloparent! :slight_smile:

Thanks,
Tommy

32

Hello,
the problem is the timezone as mentioned before, so I started testing different timezones, and also trying to add/remove some milli-seconds depending (I sync with https://time.is/) and I then generate the signature on the server as mentioned here as a solution, but what I did is for testing purposes only.

so bottom line, you need to have the exact same time as your timezone time.

33

Happy to hear you got it working! :slight_smile:

-Tommy

34

@tommy I am using the latest Websdk version 1.8.1 for my Angular and C# project. I generated the signature using given example here: https://marketplace.zoom.us/docs/sdk/native-sdks/web/build/signature

It is working fine on local but after deploying it on the production IIS server, it is giving The signature has expired. with Error code 3705 error. The server’s timezone is UTC + 5:30.

I tried in Firefox and as well in Chrome brower.

Can you please help me to sort out this issue asap?

35

Hey @dipapatra2012,

Can you please see if it works with just UTC time? The 5:30 + is most likely causing the issue.

Thanks,
Tommy

36

We getting The signature has expired with Error code 3705 error in some of the system.But same meeting working in other system. we tried in Chrome and IE browser.
Can you help us to sort out this issue asap?

37

Hey @techaravi,

Please share the code you are using to generate your Web SDK signature, as well as one of your signatures for a test meeting where you are seeing the same issue. :slight_smile:

Thanks,
Tommy

38

We are using Version 1.7.9. The below code using to generate signature
ZoomMtg.generateSignature({
meetingNumber: config.mn,
apiKey: API_KEY,
apiSecret: API_SECRET,
role: config.role,
success: function(res) {
console.log(res.result);
},
error: function(res) {
console.log(res);
}
});

We are getting the error while joining the meeting.And its happening in some of the machine, same meeting working in other machine.

39

Hey @techaravi,

Thank you, can you double check the time settings on your machine, or generate the signature on the server side. You can use this sample app, and it should work:

Thanks,
Tommy

40

I had this issue.
Steps I took to solve it are

  1. Make sure you are using jwt token API KEY and API SECRET.
  2. Check your system time. This error will come if your local device time is wrongly set or wrong time zone.

Hope this helps someone.

1 Like