Jitsi Authentication - Prosody Error

Hi,

I have installed jitsi-meet with jwt authentication following this steps: Jitsi Installation with JWT Support on Ubuntu 18.04 LTS – Doganbros

I have error when I request meet.domain.com/test?jwt=Token

|Jan 05 21:49:32 conference.meet.domain.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host meet.domain.com!|
|---|---|---|
|Jan 05 21:49:32 meet.domain.com:muc_lobby_rooms|info|Lobby component loaded lobby.meet.domain.com|
|Jan 05 21:49:32 meet.domain.com:tls|info|Certificates loaded|
|Jan 05 21:49:32 portmanager|info|Activated service 'http' on [::]:5280, [*]:5280|
|Jan 05 21:49:32 portmanager|error|Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281|
|Jan 05 21:49:32 portmanager|error|Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281|
|Jan 05 21:49:32 portmanager|info|Activated service 'https' on no ports|
|Jan 05 21:49:36 conference.meet.domain:muc_domain_mapper|warn|Session filters applied|
|Jan 05 21:49:36 c2s55c56f935a00|info|Client connected|
|Jan 05 21:49:38 c2s55c56f935a00|info|Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)|
|Jan 05 21:49:38 c2s55c56f935a00|info|Authenticated as jvb@auth.meet.domain.com|
|Jan 05 21:49:41 conference.meet.domain.com:muc_domain_mapper|warn|Session filters applied|
|Jan 05 21:49:41 mod_bosh|info|New BOSH session, assigned it sid '81e26bef-1063-43dd-b091-b10dbea19834'|
|Jan 05 21:49:41 bosh81e26bef-1063-43dd-b091-b10dbea19834|warn|No available SASL mechanisms, verify that the configured authentication module is working|
|Jan 05 21:49:52 bosh81e26bef-1063-43dd-b091-b10dbea19834|info|BOSH client disconnected: session close|
|Jan 05 21:50:07 conference.meet.domain.com:muc_domain_mapper|warn|Session filters applied|
|Jan 05 21:50:07 mod_bosh|info|New BOSH session, assigned it sid '62e14d10-5086-407b-9f64-ac4a4b86b3da'|
|Jan 05 21:50:07 bosh62e14d10-5086-407b-9f64-ac4a4b86b3da|warn|No available SASL mechanisms, verify that the configured authentication module is working|
|Jan 05 21:50:11 bosh62e14d10-5086-407b-9f64-ac4a4b86b3da|info|BOSH client disconnected: session close|
|Jan 05 21:50:12 conference.meet.domain.com:muc_domain_mapper|warn|Session filters applied|
|Jan 05 21:50:12 mod_bosh|info|New BOSH session, assigned it sid 'f9c9adbc-7a01-4dc3-8b85-9a65457594b3'|
|Jan 05 21:50:12 boshf9c9adbc-7a01-4dc3-8b85-9a65457594b3|warn|No available SASL mechanisms, verify that the configured authentication module is working|
|Jan 05 21:50:26 boshf9c9adbc-7a01-4dc3-8b85-9a65457594b3|info|BOSH client disconnected: session close|
|Jan 05 21:50:28 conference.meet.domain.com:muc_domain_mapper|warn|Session filters applied|
|Jan 05 21:50:28 mod_bosh|info|New BOSH session, assigned it sid '070bb834-5fbf-4f33-a42c-7a6b203d3caa'|
|Jan 05 21:50:28 bosh070bb834-5fbf-4f33-a42c-7a6b203d3caa|warn|No available SASL mechanisms, verify that the configured authentication module is working|
|Jan 05 21:50:31 bosh070bb834-5fbf-4f33-a42c-7a6b203d3caa|info|BOSH client disconnected: session close|

mod_auth_token.lua exist in prosody-plugins
and also plugin_paths = { “usr/share/jitsi-meet/prosody-plugins/” } exist at the top of …/conf.avail/domain.cfg.lua

No problem with these lines. Are there any other problems?

mod_token_verification is usally used.

@emrah Thank you for reply!

I re-installed SSL certs, and also mod_token_verification is inside plugins dir.

But still I have same issue.

Uncomment the following line in the Prosody config

https_ports = { };
Jan 06 12:59:48 portmanager	info	Activated service 'http' on [::]:5280, [*]:5280
Jan 06 12:59:48 portmanager	info	Activated service 'https' on no ports
Jan 06 12:59:48 portmanager	info	Activated service 'c2s' on [::]:5222, [*]:5222
Jan 06 12:59:48 portmanager	info	Activated service 'legacy_ssl' on no ports
Jan 06 12:59:48 meet.domain.com:tls	info	Certificates loaded
Jan 06 12:59:48 meet.domain.com:muc_lobby_rooms	info	Lobby component loaded lobby.meet.domain.com
Jan 06 12:59:48 auth.meet.domain.com:tls	info	Certificates loaded
Jan 06 12:59:48 general	info	Starting speakerstats for conference.meet.domain.com
Jan 06 12:59:48 speakerstats.meet.domain.com:speakerstats_component	info	No muc component found, will listen for it: conference.meet.domain.com
Jan 06 12:59:48 speakerstats.meet.domain.com:tls	info	Certificates loaded
Jan 06 12:59:48 speakerstats.meet.domain.com:speakerstats_component	info	Hook to muc events on conference.meet.domain.com
Jan 06 12:59:48 conferenceduration.meet.domain.com:conference_duration_component	info	Hook to muc events on conference.meet.domain.com
Jan 06 12:59:48 conference.meet.domain.com:tls	info	Certificates loaded
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host conference.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host speakerstats.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host lobby.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host auth.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host focus.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host internal.auth.meet.domain.com!
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host conferenceduration.meet.domain.com!
Jan 06 12:59:48 localhost:tls	info	Certificates loaded
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host localhost!
Jan 06 12:59:48 guest.meet.domain.com:auth_token	warn	WARNING - empty tokens allowed
Jan 06 12:59:48 modulemanager	error	Error initializing module 'auth_token' on 'guest.meet.domain.com': /usr/share/jitsi-meet/prosody-plugins/mod_auth_token.lua:50: attempt to call method 'hook_global_global' (a nil value)
stack traceback:
	/usr/share/jitsi-meet/prosody-plugins/mod_auth_token.lua:50: in main chunk
	[C]: in function 'xpcall'
	/usr/lib/prosody/core/modulemanager.lua:183: in function 'do_load_module'
	/usr/lib/prosody/core/modulemanager.lua:261: in function 'load'
	/usr/lib/prosody/core/usermanager.lua:67: in function '?'
	/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
	(...tail calls...)
	/usr/lib/prosody/core/hostmanager.lua:108: in function 'activate'
	/usr/lib/prosody/core/hostmanager.lua:58: in function '?'
	/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
	(...tail calls...)
	/usr/lib/prosody/util/startup.lua:393: in function 'prepare_to_start'
	/usr/lib/prosody/util/startup.lua:629: in function 'f'
	/usr/lib/prosody/util/async.lua:139: in function 'func'
	/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
Jan 06 12:59:48 guest.meet.domain.com:tls	info	Certificates loaded
Jan 06 12:59:48 conference.meet.domain.com:muc_domain_mapper	info	Loading mod_muc_domain_mapper for host guest.meet.domain.com!
Jan 06 12:59:51 conference.meet.domain.com:muc_domain_mapper	warn	Session filters applied
Jan 06 12:59:51 c2s561ae9544ae0	info	Client connected
Jan 06 12:59:53 c2s561ae9544ae0	info	Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Jan 06 12:59:54 c2s561ae9544ae0	info	Authenticated as jvb@auth.meet.domain.com
Jan 06 13:01:04 conference.meet.domain.com:muc_domain_mapper	warn	Session filters applied
Jan 06 13:01:04 mod_bosh	info	New BOSH session, assigned it sid '98e276b3-7feb-4a76-8a01-e42d07725faa'
Jan 06 13:01:04 bosh98e276b3-7feb-4a76-8a01-e42d07725faa	warn	No available SASL mechanisms, verify that the configured authentication module is working
Jan 06 13:01:11 bosh98e276b3-7feb-4a76-8a01-e42d07725faa	info	BOSH client disconnected: session close
Jan 06 13:01:12 conference.meet.domain.com:muc_domain_mapper	warn	Session filters applied
Jan 06 13:01:12 mod_bosh	info	New BOSH session, assigned it sid 'a87b13d1-0087-4349-ae32-3527c015ddaf'
Jan 06 13:01:12 bosha87b13d1-0087-4349-ae32-3527c015ddaf	warn	No available SASL mechanisms, verify that the configured authentication module is working

That is log of prosody now

I re-create VPS and re-install again all things and solved this issue.

And after reinstallation I have same issue, so I changed mod_auth_token in prosody plugins, I used this one:

Steps:
Installation - Jitsi stable, prosody 11, Ubuntu 18.04, working - Pastebin.com
Configuration - Jitsi Installation with JWT Support on Ubuntu 18.04 LTS – Doganbros

Paste your prosody log here