Converse + Prosody

[febaac]

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.15.1
What app is this about: Converse + Prosody

Describe your issue

I have Prosody installed and configured, which works without problems on a daily basis. I also have Converse installed, but I have not been able to get Converse to log in, either with my Prosody server account or with an account from another server (external, not running on Yunohost).

When I enter the credentials user@server.org and the password, the login page only displays a flashing ‘dot’, as if it were ‘loading’, but it does nothing, does not return an error, and does not complete the process.

This happens with Converse installed on my main domain (example.org), where Prosody is installed, or on a subdomain (chat.example.org). I can’t find any information on this forum or on the web.

I also can’t find where to look for a log file to see possible errors specific to Converse.

In my Prosody configuration file, I added:

inside: modules_enabled = {
… other modules …
“conversejs”;
}

Below is the Prosody log, where the following stands out (at least to me):

´ modulemanager: Unable to load module ‘conversejs’: /usr/lib/prosody/modules/share/lua/5.4/mod_conversejs/mod_conversejs.lua: No such file or directory´

I tried to install that module using the methods I found on the web, but without success.

I would appreciate some guidance on how to solve this problem, which I have been trying to fix for months without success.

Translated with DeepL.com (free version)

Share relevant logs or error messages

LOGFILE: journalctl
ago 24 21:37:51 systemd[1]: prosody.service: Consumed 2.235s CPU time.
ago 24 21:37:51 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:02:59 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:03:00 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:03:00 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:03:00 systemd[1]: prosody.service: Consumed 1.495s CPU time.
ago 24 22:03:00 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:17:08 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:17:09 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:17:09 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:17:09 systemd[1]: prosody.service: Consumed 1.616s CPU time.
ago 24 22:17:09 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:20:21 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:20:22 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:20:22 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:20:22 systemd[1]: prosody.service: Consumed 1.918s CPU time.
ago 24 22:20:28 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:21:40 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:21:40 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:21:40 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:21:40 systemd[1]: prosody.service: Consumed 1.110s CPU time.
ago 24 22:21:40 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:23:49 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:23:50 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:23:50 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:23:50 systemd[1]: prosody.service: Consumed 1.694s CPU time.
ago 24 22:23:50 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:26:39 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:26:40 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:26:40 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:26:40 systemd[1]: prosody.service: Consumed 1.848s CPU time.
– Boot 5ecf891e43894ba7930aa3620b5f7fef –
ago 24 22:28:06 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:40:05 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:40:06 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:40:06 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:40:06 systemd[1]: prosody.service: Consumed 2.894s CPU time.
ago 24 22:41:04 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:41:06 prosody[4373]: modulemanager: Unable to load module ‘conversejs’: /usr/lib/prosody/modules/share/lua/5.4/mod_conversejs/mod_conversejs.lua: No such file or directory
ago 24 22:47:44 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 24 22:47:46 systemd[1]: prosody.service: Deactivated successfully.
ago 24 22:47:46 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 24 22:47:46 systemd[1]: prosody.service: Consumed 2.739s CPU time.
– Boot 98db96f1b5204be5b7986582222c391e –
ago 24 22:49:08 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 24 22:49:18 prosody[1410]: modulemanager: Unable to load module ‘conversejs’: /usr/lib/prosody/modules/share/lua/5.4/mod_conversejs/mod_conversejs.lua: No such file or directory
ago 25 16:30:15 systemd[1]: Stopping prosody.service - Prosody XMPP Server…
ago 25 16:30:16 systemd[1]: prosody.service: Deactivated successfully.
ago 25 16:30:16 systemd[1]: Stopped prosody.service - Prosody XMPP Server.
ago 25 16:30:16 systemd[1]: prosody.service: Consumed 9.793s CPU time.
– Boot bd561f9f6849486d861d873f9d7a34d8 –
ago 25 16:31:47 systemd[1]: Started prosody.service - Prosody XMPP Server.
ago 25 16:31:56 prosody[1448]: modulemanager: Unable to load module ‘conversejs’: /usr/lib/prosody/modules/share/lua/5.4/mod_conversejs/mod_conversejs.lua: No such file or directory

EDIT>>

This error /usr/lib/prosody/modules/share/lua/5.4/mod_conversejs/mod_conversejs.lua: No such file or directory is related to my modification of the Prosody configuration. It has nothing to do with Converse… I’ll keep trying.

[anubis]

Hello,
how did you installed Prosody ? via apt or the Yunohost App?
Using the Prosody App and Converse.js App was reported to work (prosody_ynh/doc/DESCRIPTION.md at master · YunoHost-Apps/prosody_ynh · GitHub )

[ericg]

@febaac

conversejs

I could be wrong, but I don’t think you need to enable the conversejs module in Prosody.

[febaac]

Everything was installed using the yunohost app.

[febaac]

Well, the problem isn’t my converse instance… since I created an account on suchat.org and I can use it.

With my self-hosted xmpp account (prosody), I can’t log in to https://chat.conversejs.org either.

---

I believe the problem is because this ‘module/extension’ is not working.

### For XEP-0156: Discovering Alternative XMPP Connection Methods (HTTP) :*

[anubis]

If you installed the Converse app GitHub - YunoHost-Apps/converse_ynh: Converse package for YunoHost you should not modify your Prosody configuration file.
Can you confirm that using your self-hosted XMPP account on your self-hosted Converse is working?

If not, try to connect your account with Conversations.

If not, check whether Prosody is running properly with sudo prosodyctl check.

[febaac]

Hi. My self-hosted XMPP account works without problems, I use it daily with Monocles (and I have used it with Conversations as well) the problem is that it does not connect to my self-hosted Converse instance or any other (like the official one)
Is there any extra “open” port required (for prosody) that yunohost does not report to be opened?

And I think I mentioned it before, on yunohost v11 with metronome and Converse everything was working.

This weekend maybe I’ll try to install in a virtual machine everything from scratch and see what happens.
Try prosody and metronome + converse.

[febaac]

Converse self-hosted>

LOGFILE: /var/log/prosody/prosody.log
Aug 31 00:31:42 c2s55f9d873ab10	info	Client disconnected: connection closed
Aug 31 00:31:42 portmanager	info	Deactivated service 's2s'
Aug 31 00:31:42 portmanager	info	Deactivated service 's2s_direct_tls'
Aug 31 00:31:42 s2sin55f9d87baed0	info	Incoming s2s stream gnlug.org->ismondo.org closed: Received SIGTERM
Aug 31 00:31:42 s2sout55f9d87e7b10	info	Outgoing s2s stream ismondo.org->salas.undernet.uy closed: Received SIGTERM
Aug 31 00:31:42 s2sin55f9d8585c90	info	Incoming s2s stream salas.buzon.uy->ismondo.org closed: Received SIGTERM
Aug 31 00:31:42 s2sin55f9d874acd0	info	Incoming s2s stream salas.undernet.uy->ismondo.org closed: Received SIGTERM
Aug 31 00:31:42 s2sout55f9d8a72ee0	info	Outgoing s2s stream ismondo.org->salas.buzon.uy closed: Received SIGTERM
Aug 31 00:31:42 mod_s2s	info	Waiting for sessions to close
Aug 31 00:31:42 general	info	Shutting down...
Aug 31 00:31:42 general	info	Shutdown status: Cleaning up
Aug 31 00:31:42 general	info	Shutdown complete
Aug 31 00:31:43 startup	info	Hello and welcome to Prosody version 0.12.3
Aug 31 00:31:43 startup	info	Prosody is using the epoll backend for connection handling
Aug 31 00:31:43 portmanager	info	Activated service 'c2s' on [::]:5222, [*]:5222
Aug 31 00:31:43 portmanager	info	Activated service 'c2s_direct_tls' on no ports
Aug 31 00:31:43 portmanager	info	Activated service 'legacy_ssl' on no ports
Aug 31 00:31:43 portmanager	info	Activated service 'http' on [::1]:5280, [127.0.0.1]:5280
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for https port 5281. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for https port 5281. SNI will be required.
Aug 31 00:31:43 portmanager	info	Activated service 'https' on [::]:5281, [*]:5281
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for ismondo.org. SNI will be required.
Aug 31 00:31:43 ismondo.org:http	info	Serving 'websocket' at https://ismondo.org:5281/xmpp-websocket
Aug 31 00:31:43 ismondo.org:cloud_notify	info	Module loaded
Aug 31 00:31:43 portmanager	info	Activated service 'proxy65' on [::]:5000, [*]:5000
Aug 31 00:31:43 ismondo.org:http	info	Serving 'bosh' at https://ismondo.org:5281/http-bind
Aug 31 00:31:43 portmanager	info	Activated service 's2s' on [::]:5269, [*]:5269
Aug 31 00:31:43 portmanager	info	Activated service 's2s_direct_tls' on no ports
Aug 31 00:31:43 ismondo.org:csi_battery_saver	info	e94c: Successfully loaded module
Aug 31 00:31:43 ismondo.org:tls	info	Certificates loaded
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for ismondo.org. SNI will be required.
Aug 31 00:31:43 muc.ismondo.org:tls	info	Certificates loaded
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for muc.ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for muc.ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for localhost. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for localhost. SNI will be required.
Aug 31 00:31:43 localhost:tls	info	Certificates loaded
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for localhost. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for localhost. SNI will be required.
Aug 31 00:31:43 xmpp-upload.ismondo.org:http	info	Serving 'upload' at https://xmpp-upload.ismondo.org/upload
Aug 31 00:31:43 xmpp-upload.ismondo.org:http_upload	info	URL: <https://xmpp-upload.ismondo.org/upload> - Ensure this can be reached by users
Aug 31 00:31:43 xmpp-upload.ismondo.org:http_upload	info	Storage path: '/var/xmpp-upload/ismondo.org/upload/'
Aug 31 00:31:43 xmpp-upload.ismondo.org:tls	info	Certificates loaded
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for xmpp-upload.ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for xmpp-upload.ismondo.org. SNI will be required.
Aug 31 00:31:43 pubsub.ismondo.org:tls	info	Certificates loaded
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for pubsub.ismondo.org. SNI will be required.
Aug 31 00:31:43 certmanager	info	No certificate present in SSL/TLS configuration for pubsub.ismondo.org. SNI will be required.

[pitchum]

Hi, I think I found a solution for your issue @febaac but I’ll need some time to prepare a proper fix.

Long story: the converse app tries to join an hard-coded Bosh URL (something like https://domain.tld/http-bind/ ) which does not work with the current version of prosody app.
I’ll propose a PR for converse to avoid that hard-coded URL and instead use the mechanism of “Discovering Alternative XMPP Connection Methods” (XEP-0156).

If you don’t want to wait, you may try the following workaround:

1. update prosody app to version 0.12.4~ynh103 (now implementing XEP-0156)
2. manually patch the file /var/www/converse/index.html by removing the line containing “bosh_service_url: …”

And it shoud be enough.

[febaac]

Thank you! After updating prosody, I was able to log into my Converse instance.

[pitchum]

I confirm there is nothing to fix in Converse app, that’s good news