dinoxim/dinox

[Bug]: Connection to XMPP server (ejabberd) failed with (START)TLS error #34

New issue

Closed

opened 2026-10-28 14:22:43 +01:00 by vovan · 4 comments

vovan commented

2026-10-28 14:22:43 +01:00

DinoX version

2.3.2

Installation method

AppImage (x86_64)

Operating system

Gentoo

OS details (if "Other" or additional info)

No response

Desktop environment

XFCE 4

Display server

X11 / Xorg

XMPP server (domain)

vovan.nl

XMPP server software

ejabberd

Encryption active?

None (unencrypted)

Affected area

Connection / Login

What happened?

Expected: Successful connection to the server
Actual: Connection failed with the following error message (dinox:8): xmpp-vala-WARNING **: 13:42:39.837: stream_connect.vala:148: Could not establish XMPP session with xxxxx:5222: Failed connecting to xxxxx:5222 (starttls): TLS support is not available
Notes:

Other clients like Gajim and Dino on Linux and Conversation on Android don't have authentication issues.
SCRAM is disabled in dinox advanced settings as can't be used with ejabberd + LDAP authentication

Steps to reproduce

Started DinoX
Fill authentication info and disable SCRAM
Sign in leads to error message "Something went wrong" in GUI

Log output

No response

Additional context

No response

Checklist

I have searched existing issues for duplicates
I am using the latest version of DinoX
I have read the DEBUG guide
I have attached log output (if applicable)

### DinoX version 2.3.2 ### Installation method AppImage (x86_64) ### Operating system Gentoo ### OS details (if "Other" or additional info) _No response_ ### Desktop environment XFCE 4 ### Display server X11 / Xorg ### XMPP server (domain) vovan.nl ### XMPP server software ejabberd ### Encryption active? None (unencrypted) ### Affected area Connection / Login ### What happened? **Expected**: Successful connection to the server **Actual**: Connection failed with the following error message `(dinox:8): xmpp-vala-WARNING **: 13:42:39.837: stream_connect.vala:148: Could not establish XMPP session with xxxxx:5222: Failed connecting to xxxxx:5222 (starttls): TLS support is not available` Notes: - Other clients like Gajim and Dino on Linux and Conversation on Android don't have authentication issues. - SCRAM is disabled in dinox advanced settings as can't be used with ejabberd + LDAP authentication ### Steps to reproduce 1. Started DinoX 2. Fill authentication info and disable SCRAM 3. Sign in leads to error message "Something went wrong" in GUI ### Log output _No response_ ### Additional context _No response_ ### Checklist - [x] I have searched [existing issues](https://git.dinox.im/dinoxim/dinox/issues) for duplicates - [x] I am using the [latest version](https://git.dinox.im/dinoxim/dinox/releases/latest) of DinoX - [ ] I have read the [DEBUG guide](https://git.dinox.im/dinoxim/dinox/src/branch/master/docs/internal/DEBUG.md) - [ ] I have attached log output (if applicable)

vovan added the

bug

label

2026-10-28 14:22:43 +01:00

dinoxim referenced this issue from a commit

2026-10-28 14:54:45 +01:00

fix(appimage): bundle the GIO TLS backend

dinoxim commented

2026-10-28 15:02:07 +01:00

Owner

Thank you for the report and the clear reproduction steps — I was able to reproduce this with the published 2.3.2 AppImage.

The AppImage was missing the GIO TLS module (libgiognutls.so). It could work when a compatible module was available on the host, but otherwise GIO reported “TLS support is not available” before authentication began. This particular error is caused by our packaging, not by your LDAP setup or SCRAM setting.

The fix is in a0db5a3f: it bundles the module, its dependencies and module cache, and configures the module path in AppRun. I tested TLS initialization with the host's GIO modules hidden and added packaging checks to catch this omission in future builds. The GNOME 50 runtime used by our Flatpak also passed the TLS initialization test.

The updated AppImage still needs to be built and uploaded; the current 2.3.2 download does not contain this fix yet. Once the updated package is available, a retest on your Gentoo system would be very helpful. I have not yet verified a complete login on your setup.

Thanks again for helping us catch this!

Thank you for the report and the clear reproduction steps — I was able to reproduce this with the published 2.3.2 AppImage. The AppImage was missing the GIO TLS module (`libgiognutls.so`). It could work when a compatible module was available on the host, but otherwise GIO reported “TLS support is not available” before authentication began. This particular error is caused by our packaging, not by your LDAP setup or SCRAM setting. The fix is in [a0db5a3f](https://git.dinox.im/dinoxim/dinox/commit/a0db5a3f): it bundles the module, its dependencies and module cache, and configures the module path in AppRun. I tested TLS initialization with the host's GIO modules hidden and added packaging checks to catch this omission in future builds. The GNOME 50 runtime used by our Flatpak also passed the TLS initialization test. The updated AppImage still needs to be built and uploaded; the current 2.3.2 download does not contain this fix yet. Once the updated package is available, a retest on your Gentoo system would be very helpful. I have not yet verified a complete login on your setup. Thanks again for helping us catch this!

dinoxim commented

2026-10-28 15:03:50 +01:00

Owner

https://git.dinox.im/dinoxim/dinox/actions/runs/284/jobs/4/attempt/1 if finish you can download appimage with bugfix

👍 1

dinoxim closed this issue

2026-10-28 18:10:40 +01:00

vovan commented

2026-10-29 06:05:31 +01:00

Author

@dinoxim wrote in #34 (comment):

https://git.dinox.im/dinoxim/dinox/actions/runs/284/jobs/4/attempt/1 if finish you can download appimage with bugfix

Sorry for commenting on the closed issue, but artifact dinox-appimage of this job is not available (anymore?).

@dinoxim wrote in https://git.dinox.im/dinoxim/dinox/issues/34#issuecomment-169: > https://git.dinox.im/dinoxim/dinox/actions/runs/284/jobs/4/attempt/1 if finish you can download appimage with bugfix Sorry for commenting on the closed issue, but artifact `dinox-appimage` of this job is not available (anymore?).

dinoxim commented

2026-10-29 07:07:33 +01:00

Owner

The artefacts have an expiry date; they were automatically deleted at 00:00. I’ll be releasing a new version later today, so please bear with me. It’s therefore not worth building an AppImage again right now, as that would take over two hours.

👍 1