Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

with v4.14.5 php backend, error OT_AUTHENTICATION_ERROR: token has expired (1004) #344

Open
garrettboone opened this issue Dec 14, 2024 · 1 comment

Comments

@garrettboone
Copy link

garrettboone commented Dec 14, 2024

Both sides of call have error showing OT_AUTHENTICATION_ERROR: token has expired (1004)

Expected Behavior

Call connects fine.

Current Behavior

When upgrading to 4.14.5 it breaks something for us, however if we downgrade to v4.14.4 on the backend our code works fine without new packages (sodium, jwt, etc)

Not sure where this error is being caused.

Person A calls B.
A's publisher is seen by B after subscription.
B's publisher is never seen by A, both sides have error.

Environment

This behavior is seen in two systems:

  1. Centos 7, php83, NGINX
  2. WSL: Ubuntu Linux 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
"Error: token has expired (1004)
    at onSessionInfoError (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:51486:55)
    at invokeCallback (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:424:31)
    at publish (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:413:23)
    at publishRejection (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:371:19)
    at MutationObserver.flush (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:227:21)"

package.lock says

node_modules/@opentok/client": {
      "version": "2.28.5"

Is this the correct repo?

@dragonmantank
Copy link
Contributor

The other repo was the correct one :P I'll reopen that ticket and let you know here soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants