Prosody issue after upgrade to stable-7577
See original GitHub issueI recently upgraded to stable channel, and I am getting various errors on prosody and web console.
It appears issues with prosody plugins where it fails to authenticate participant creating websocket stream error on frontend.
BTW, rolling back to previous stable channel stops the problem.
web console Errors:
2022-08-08T05:50:54.897Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Strophe: WebSocket stream error: undefined-condition - No stream features to proceed with Script: null Line: null Column: null StackTrace: Error: Strophe: WebSocket stream error: undefined-condition - No stream features to proceed with
at ut.Strophe.log (https://domain.example.com/libs/lib-jitsi-meet.min.js?v=6436:2:448804)
at Object.error (https://domain.example.com?v=6436:2:146409)
at O.Websocket._check_streamerror (https://domain.example.com/libs/lib-jitsi-meet.min.js?v=6436:2:182511)
at O.Websocket._connect_cb (https://domain.example.com/libs/lib-jitsi-meet.min.js?v=6436:2:182925)
at I.Connection._connect_cb (https://domain.example.com/libs/lib-jitsi-meet.min.js?v=6436:2:158664)
at O.Websocket._connect_cb_wrapper (https://domain.example.com/libs/lib-jitsi-meet.min.js?v=6436:2:184430)
r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:532
window.onerror @ middleware.js:110
callErrorHandler @ GlobalOnErrorHandler.js:61
ut.Strophe.log @ strophe.util.js:88
error @ strophe.umd.js:1392
_check_streamerror @ strophe.umd.js:5433
_connect_cb @ strphe.umd.js:3229
...
Logger.js:154 2022-08-08T05:50:54.897Z [modules/xmpp/strophe.util.js] <ut.Strophe.log>: Strophe: WebSocket stream error: undefined-condition - No stream features to proceed with
r @ Logger.js:154
ut.Strophe.log @ strophe.util.js:89
error @ strophe.umd.js:1392
_check_streamerror @ strophe.umd.js:5433
_connect_cb @ strophe.umd.js:5479
...
Logger.js:154 2022-08-08T05:50:54.897Z [modules/xmpp/xmpp.js] <sa.connectionHandler>: (TIME) Strophe connfail[undefined-condition]: 1881.6000000238419
Logger.js:154 2022-08-08T05:50:54.897Z [modules/xmpp/xmpp.js] <sa.connectionHandler>: (TIME) Strophe disconnected: 1881.9000000059605
Logger.js:154 2022-08-08T05:50:54.898Z [modules/statistics/statistics.js] <Tn.sendAnalyticsAndLog>: {"type":"operational","action":"connection.failed","attributes":{"error_type":"connection.otherError","error_message":"undefined-condition","suspend_time":0,"time_since_last_success":null}}
index.js:154 2022-08-08T05:50:54.898Z [connection.js] <r.s>: CONNECTION FAILED: connection.otherError
i @ index.js:154
s @ connection.js:173
r.emit @ events.js:158
connectionHandler @ xmpp.js:376
_stropheConnectionCb @ XmppConnection.js:308
_changeConnectStatus @ strophe.umd.js:3011
_doDisconnect @ strophe.umd.js:3052
_interceptDoDisconnect @ strophe.stream-management.js:218
_check_streamerror @ strophe.umd.js:5437
_connect_cb @ strophe.umd.js:5479
...
index.js:154 2022-08-08T05:50:54.899Z [features/base/conference] JWT error: undefined-condition
i @ index.js:154
(anonymous) @ middleware.any.js:285
e @ connection.js:131
r.emit @ events.js:158
connectionHandler @ xmpp.js:376
_stropheConnectionCb @ XmppConnection.js:308
_changeConnectStatus @ strophe.umd.js:3011
_doDisconnect @ strophe.umd.js:3052
_interceptDoDisconnect @ strophe.stream-management.js:218
_check_streamerror @ strophe.umd.js:5437
_connect_cb @ strophe.umd.js:5479
_connect_cb @ strophe.umd.js:3229
_connect_cb_wrapper @ strophe.umd.js:5582
Show 14 more frames
index.js:154 2022-08-08T05:50:54.899Z [features/base/conference] JWT parsing error: ['- invalid `nbf` value']
i @ index.js:154
(anonymous) @ middleware.any.js:286
(anonymous) @ middleware.any.js:304
o @ middleware.ts:44
(anonymous) @ middleware.ts:7
...
e @ connection.js:131
r.emit @ events.js:158
connectionHandler @ xmpp.js:376
_stropheConnectionCb @ XmppConnection.js:308
_changeConnectStatus @ strophe.umd.js:3011
_doDisconnect @ strophe.umd.js:3052
_interceptDoDisconnect @ strophe.stream-management.js:218
_check_streamerror @ strophe.umd.js:5437
...
Show 14 more frames
index.js:154 2022-08-08T05:50:54.902Z [features/overlay] <Roe.componentDidMount>: The conference will be reloaded after 28 seconds.
Logger.js:154 2022-08-08T05:50:54.906Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: connection.otherError Script: null Line: null Column: null StackTrace: n/a
r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:532
window.onunhandledrejection @ middleware.js:127
domain.example…orageContent=null:1 Uncaught (in promise) connection.otherError
Prosody:
Client connected
2022-08-08T05:55:36.367473896Z c2s55dd714746a0 debug Sending WebSocket handshake
2022-08-08T05:55:36.647115581Z mod_websocket debug Websocket received frame: opcode=1, 96 bytes
2022-08-08T05:55:36.647196556Z runner1gLaZmXfpHMR debug creating new coroutine
2022-08-08T05:55:36.647232722Z c2s55dd714746a0 debug Client sent opening <stream:stream> to domain.example.com
2022-08-08T05:55:36.647295749Z c2s55dd714746a0 debug Sending[c2s_unauthed]: <open xml:lang='en' xmlns='urn:ietf:params:xml:ns:xmpp-framing' id='df1997ed-b7e3-46bf-9be7-e0ed7786e7f0' version='1.0' from='domain.example.com'>
2022-08-08T05:55:36.647354521Z c2s55dd714746a0 debug Sent reply <stream:stream> to client
2022-08-08T05:55:36.647436712Z c2s55dd714746a0 debug SASL mechanisms supported by handler:
2022-08-08T05:55:36.647486693Z c2s55dd714746a0 warn No available SASL mechanisms, verify that the configured authentication module 'token' is loaded and configured correctly
2022-08-08T05:55:36.647494128Z c2s55dd714746a0 warn No stream features to offer on secure session. Check authentication settings.
2022-08-08T05:55:36.647563031Z c2s55dd714746a0 debug Disconnecting client, <stream:error> is: <stream:error><undefined-condition xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>No stream features to proceed with</text></stream:error>
2022-08-08T05:55:36.647571277Z c2s55dd714746a0 debug Sending[c2s_unauthed]: <stream:error>
2022-08-08T05:55:36.647667678Z c2s55dd714746a0 debug Sending[c2s_unauthed]: <close xmlns='urn:ietf:params:xml:ns:xmpp-framing'>
2022-08-08T05:55:36.647675213Z c2s55dd714746a0 debug c2s stream for <192.168.195.44> closed: No stream features to proceed with
2022-08-08T05:55:36.652073529Z c2s55dd714746a0 debug Destroying session for (unknown) ((unknown)@domain.example.com): No stream features to proceed with
2022-08-08T05:55:36.652108541Z conncl2i9vfg9F9f debug Close after writing remaining buffered data
2022-08-08T05:55:36.652159043Z conncl2i9vfg9F9f debug Closing now
2022-08-08T05:55:36.652165148Z c2s55dd714746a0 info Client disconnected: connection closed
2022-08-08T05:55:36.652168222Z c2s55dd714746a0 debug Destroying session for (unknown) ((unknown)@(unknown))
Issue Analytics
- State:
- Created a year ago
- Comments:24 (24 by maintainers)
Top Results From Across the Web
Audio/Video not working on latest version of JVB 2.0.7577
I noticed after upgrade of JVB and Jicofo, Prosody to latest versions. jitsi-videobridge_2.2-18-gade06bf8 2.0.7577 ...
Read more >0.12.0 - Prosody IM
After the upgrade, you can review the new configuration file and incorporate any changes into your existing config. To be clear, it is...
Read more >Prosody issue after upgrade to stable-7577 - Devscope.io
Issue. I recently upgraded to stable channel, and I am getting various errors on prosody and web console. It appears issues with prosody...
Read more >Prosody and Articulation - Apraxia Kids
The following table summarizes common speech characteristics or errors of CAS and how they interact with prosody. Table 1. Effects of CAS Speech ......
Read more >Automated Assessment of Prosody Production - PMC - NCBI
Many of these issues are not specific to perceptual judgment of speech; in fact, ... The child's task is to repeat after the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@saghul
No available SASL mechanisms, verify that the configured authentication module 'token' is loaded and configured correctlythis is normally when token module did not load on startup.You can use this: https://github.com/jitsi/jitsi-meet/blob/c7f96de787cce94b53a78cf07f1e9dca222a3ef4/resources/prosody-plugins/util.lib.lua#L244 it returns the tenant and the roomname.