Audio/Video not working in token authentication

Hello !

I have an issue in the latest self-hosting installation with token authentication.
I can’t manage to find the solution.

When I use the “internal_hashed” authentication the system is ok, but when I switch to token the Audio/Video not activated in any way.

I have the following environment :

Ubuntu 22.04 LTD

jicofo-1.0-968-1
jitsi-meet-web-config-1.0.6854-1
jitsi-meet-web-1.0.6854-1
jitsi-videobridge2-2.2-63-g252d14bc-1
jitsi-meet-tokens-1.0.6854-1

prosody-0.12.1-1~jammy1

In server logs JVB:
JVB 2022-12-10 17:30:55.699 WARNING: [34] [hostname=localhost id=shard] MucClient.setPresenceExtensions#459: Cannot set presence extension: not connected.
JVB 2022-12-10 17:30:55.823 WARNING: [28] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$9#632: Error connecting:
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: ‘RFC 6120 A/AAAA Endpoint + [localhost:5222] (localhost/127.0.0.1:5222)’ failed because: java.net.ConnectException: Connection refused (Connection refused)
at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:627)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

In server logs jicofo:
Jicofo 2022-12-10 17:30:56.168 SEVERE: [29] [xmpp_connection=client] XmppProviderImpl.doConnect#216: Failed to connect/login: The following addresses failed: ‘RFC 6120 A/AAAA Endpoint + [localhost:5222] (localhost/127.0.0.1:5222)’ failed because: java.net.ConnectException: Connection refused (Connection refused)
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: ‘RFC 6120 A/AAAA Endpoint + [localhost:5222] (localhost/127.0.0.1:5222)’ failed because: java.net.ConnectException: Connection refused (Connection refused)
at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jitsi.impl.protocol.xmpp.XmppProviderImpl.doConnect(XmppProviderImpl.java:197)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

Do you have any idea on how to troubleshoot this issue ?

Thank you !

P.S I have another server jitsi (self-hosted) with token authentication on Ubuntu 18 and it has been running without problems for over a year …

prosody logs may help.

prosody log stopped at 9am this morning before i finished token authentication …

Dec 10 09:17:26 mod_posix warn Received SIGTERM
Dec 10 09:17:26 startup info Shutting down: Received SIGTERM
Dec 10 09:17:26 portmanager info Deactivated service ‘c2s’
Dec 10 09:17:26 portmanager info Deactivated service ‘c2s_direct_tls’
Dec 10 09:17:26 portmanager info Deactivated service ‘legacy_ssl’
Dec 10 09:17:26 mod_c2s info Waiting for sessions to close
Dec 10 09:17:26 c2s555da2e76de0 info Client disconnected: connection closed
Dec 10 09:17:26 portmanager info Deactivated service ‘s2s’
Dec 10 09:17:26 portmanager info Deactivated service ‘s2s_direct_tls’

What is its status?

systemctl restart prosody
systemctl status prosody

Sorry …

I forgot a ; in prosody configuration … but after entering the ; and restart prosody, in the log of prosody (prosody.err) there is

token_verification error 'app_id' must not be empty

I don’t understand why, since I entered the app_id

VirtualHost “*******”
– authentication = “token” – do not delete me
– authentication = “internal_hashed”
authentication = “token”
– Properties below are modified by jitsi-meet-tokens package config
– and authentication above is switched to “token”
app_id=“my_app_id”
app_secret=“my_password_id”
allow_empty_token = false
[…]

… but now …

it seems to work

thanks

1 Like