Trouble with JWT setup with Debian 11 and lua5.4

We followed the old installation instruction to install JWT token. However, lua5.2-dev no longer exists. Instead, we installed lua 5.4. then we have trouble with Prosody. The Prosody log is like the following:

Aug 28 01:01:17 c2s5639cd784de0 info Client connected
Aug 28 01:01:19 c2s5639cd784de0 info Client disconnected: connection closed

Also, the Prosody error log shows something like token_verification error Token XXX not allowed to join room

If we run systemctl status prosody, it shows it is active(running)

We tried to use liblua5.2-dev as well, but the problem is still there.

/var/log/jitsi/jvb.log shows the following:

JVB 2022-08-26 19:41:09.016 INFO: [18] [hostname=localhost id=shard] MucClient$2.authenticated#318: Authenticated, b=false
JVB 2022-08-26 19:41:09.040 INFO: [1] MainKt.main#147: Starting private http server
JVB 2022-08-26 19:41:09.108 INFO: [18] [hostname=localhost id=shard] MucClient$MucWrapper.join#761: Joined MUC: jvbbrewery@internal.auth.testguest3.everleagues.com
JVB 2022-08-26 19:41:09.939 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2022-08-26 19:41:10.263 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored.
JVB 2022-08-26 19:41:10.271 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
JVB 2022-08-26 19:41:10.272 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.prometheus.Prometheus registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.prometheus.Prometheus will be ignored.

Can you help us to solve this problem? If you need any further information, I can provide more.

With Ubuntu Server 20 i can still get it with apt install liblua5.2-dev (and it works)

1 Like

I tried, but I still get the token_verification error. There is no problem with the token secret and the prosody config file is correct settings (as before).

You see this when you try to connect using a token?

The same is true for Debian 11 Bullseye

Yes. When I use a token, it gives me this error.

I’ll try again.

As an alternative you may use this third-party installer

Thanks again. I will also try this installer.

It seems to be working with liblua5.2-dev. I will try again to confirm. I think the problem is coming from my token creation process.

You may try with a token from jitok

1 Like

Thank you so much!

1 Like