Hi Please suggest me something,
I’m encountering errors with my self-hosted meetings. Currently, I’m using docker compose up for each new meeting, so wouldn’t it automatically generate a new signature for each one? Is there something I might be overlooking, since errors should not occur with a new Docker instance? Also, could you explain what error codes 5 and 65535 signify?
@chunsiong.zoom Is there anything I could do to debug?
@shaheer.teczon here’s what I’ll do to debug
- run it on an x64 linux box, or docker in interactive mode, and
- generate the JWT token yourself instead of using the function provided.
@chunsiong.zoom This is already running in docker. Even in interactive mode error is same. Since JWT is valid even tested by you. I guess the issue is somewhere else. Not sure if sdk or server error.
@MaxM Kindly suggest something
@shaheer.teczon I’m using this code sample
It is not the same as the one you are using.
You should generate your own JWT token from scratch and try it on the original code sample which you are using.
@chunsiong.zoom Would be great if you could share how to generate own JWT Token?
@chunsiong.zoom sorry for hijacking this topic, but is potentially bring the transcription/closed caption features over to the linux sdk on the roadmap? we’ve just been contemplating migrating our windows bot over to a linux environment for better ease of hosting.
@xschen there are no plans for those features in the Linux SDK yet