[SimpleX Chat] Messaging platform

Hello,

The app seems to be flag as broken probably due to binaries built based from Debian 11 for both amd64 and arm64 (with OpenSSL 1).

The last pending PR is the update to v6.1.3 and built based from Debian 11 before new release YunoHost 12.

Should I had to upgrade my VM and my Raspberry Pi to Debian 12 in order to rebuilt binaries with OpenSSL 3 for the last version 6.1.3 ?

ppr

1 Like

Hello, it not running after install( Do you need additional configuration? hastebin

1 Like

Yup, log file looks the same over here. Service is not running.

If we want to debug the app you need to follow the forum template. (app version, proc arch, etc.)

YunoHost 12.0.11 (stable), amd 64 (intel N100), simplex 6.2.0~ynh1
https://paste.yunohost.org/ahajidifem.yaml

bj ta ajouter dans firwall depuis yunohost ou bien yunohost firewall xxx

j’ai vus dans tes log:
install certbot indépendant en ssh

sudo -i
apt install -y certbot
certbot --nginx -d site.tld

essaie écouter les port si est connecté

nestat -ano
#ou 
netstat -plnt | grep 443

Hello, I have just installed prosody which make use of port 5223. It gives a conflict with simplex using port 5223 for smp. Is there a way to change the standard smp port ?

I have this same error, simplex doesn’t start

Hi, very nice piece of software.

It looks like you can enroll a client on your server by generating a QR code.
It would be nice to show it on the application admin panel.
What do you think?

2 Likes

to show the QR code in the admin panel?

1 Like

Indeed!

Can you try GitHub - YunoHost-Apps/simplex_ynh at rework branch.

Simplex server information is displayed on a web page. However, I don’t know if it’s displaying all the necessary information or if we’re missing something


Do I understand correctly that simplex can only be installed on a server where ports 80 and 443 are not occupied?
At first, I got the error: Error: no HTTPS credentials: /etc/opt/simplex/web.crt, /etc/opt/simplex/web.key
I created a self-signed certificate in the folder, now the error is as follows: smp-server: Network.Socket.bind: permission denied (Permission denied)

I had to manually set up the custom domain and adjust the nginx config a bit, but after that it worked fine. Notifications were a bit spotty for me at first though.