[05:51:59]
<joeldebruijn[m]> Anybody else having an application catalog with substantially less items?
I ran in some problems installing Pleroma yesterday, so wanted to see if I could install something else for another domain. Tested with Wordpress and worked like a charm.
Wanted to see if I could install Pleroma but its missing from the catalog.
[05:53:22]
<joeldebruijn[m]> Unfilters (all apps) counts 20 at the moment
[05:58:42]
<joeldebruijn[m]> Hmmmm, sorry, was a bit confused by the LDAP SSO inlog with Wordpress, did that in the same browser sessions, so I guess I'm logged in into Yunohost as the wrond user.
[05:58:57]
<joeldebruijn[m]> * Hmmmm, sorry, was a bit confused by the LDAP SSO inlog with Wordpress, did that in the same browser session, so I guess I'm logged in into Yunohost as the wrond user.
[05:59:08]
<joeldebruijn[m]> * Hmmmm, sorry, was a bit confused by the LDAP SSO inlog with Wordpress, did that in the same browser session, so I guess I'm logged in into Yunohost as the wrong user.
[06:02:45]
<joeldebruijn[m]> Opened an incognito browser, login with admin password, same result.
[06:16:36]
<joeldebruijn[m]> Looks like this one from @flappybird https://forum.yunohost.org/t/most-applications-gone-after-php-upgrade/22969
[06:43:49]
<joeldebruijn[m]> Although I'm on php 7.4
[07:21:33]
<anant> Hi folks new to yono old to debian installs. Can i assume yono is like debian with click based full app stack deployment options. Also do i really need a domain name or is it more for routing and i can create local domains via dns of my own.
[07:33:17]
<tituspijean> *yuno 😜
I suggest you have a look to https://yunohost.org/whatsyunohost first :)
[07:34:22]
<tituspijean> You can definitely use .local domains on your own network (mDNS included), or use fake DNS entries on your router too.
[10:32:49]
<craigvb[m]> > <@joeldebruijn:matrix.org> Anybody else having an application catalog with substantially less items?
> I ran in some problems installing Pleroma yesterday, so wanted to see if I could install something else for another domain. Tested with Wordpress and worked like a charm.
> Wanted to see if I could install Pleroma but its missing from the catalog.
yup, same here, all but one app not supported, I'm guessing they've messed something up or the php8 updates that installed today (for me anyway) messed up a script, I'm sure it'll be fixed soon :)
[10:40:50]
<craigvb[m]> Just had another update come through (looked like php's again) and the application catalog's all back up and running :)
[10:55:03]
<tituspijean> > <@craigvb[m]:libera.chat> Just had another update come through (looked like php's again) and the application catalog's all back up and running :)
Yup I fixed the issue. 🙂 Update your catalog by opening the "Upgrade system" page of your webadmin, or run `sudo yunohost tools update` in your webadmin.
[10:55:13]
<tituspijean> joeldebruijn[m] ^
[11:49:47]
<joeldebruijn[m]> Thnx!!!
[13:50:36]
<tituspijean> Hiya,
I'm in the middle of migration a RPi3 from YNH v4.4.2.14 to 11, but I am facing a good old dependency issue:
```
apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
libc-dev-bin : Depends: libc6 (< 2.29) but 2.31-13+rpt2+rpi1+deb11u5 is installed
libc6-dbg : Depends: libc6 (= 2.28-10+rpt2+rpi1+deb10u1) but 2.31-13+rpt2+rpi1+deb11u5 is installed
libc6-dev : Depends: libc6 (= 2.28-10+rpt2+rpi1+deb10u1) but 2.31-13+rpt2+rpi1+deb11u5 is installed
mailutils : Depends: mailutils-common (= 1:3.5-4) but 1:3.10-3 is installed
Depends: libmailutils5 but it is not installable
openssh-sftp-server : Depends: openssh-client (= 1:7.9p1-10+deb10u2+rpt1) but 1:8.4p1-5+deb11u1 is installed
unscd : Depends: libc6 (< 2.29) but 2.31-13+rpt2+rpi1+deb11u5 is installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
```
[13:50:59]
<tituspijean> How can I fix that to proceed?
[13:58:40]
<tituspijean> (transferring between train stations now, back in 1.5 hour)
[14:50:20]
<pistrie> hi there, im not sure if this is the correct channel, but I noticed that the certificate for the demo website has expired yesterday. Just wanted to give a heads up :)
[14:53:41]
<tituspijean> Thank you for the heads-up! We will try to fix that ASAP. :)
[18:34:02]
<thatoo> Bonsoir, j'ai un curieux problème de certificat
[18:35:11]
<thatoo> ce qui est cool
[18:35:46]
<thatoo> si je vais sur https://MYDOMAIN.fr/site et que je regarde le certificat avec l'aide de Firefox, c'est OK
[18:36:20]
<thatoo> Pas avant Thu, 22 Dec 2022 06:19:41 GMT
Pas après Wed, 22 Mar 2023 06:19:40 GMT
[18:36:40]
<thatoo> mais si je veux envoyer un email depuis Thunderbird, j'obtiens une erreur
[18:38:26]
<thatoo> Ajout d'une exception de sécurité
Vous êtes en train de passer outre la façon dont Thunderbird identifie ce site
Adresse : MYDOMAIN.fr:587
[18:38:35]
<thatoo> Si je clique sur "Voir..."
[18:38:50]
<thatoo> alors le certificat est différent et les dates ne sont en effet pas les bonnes
[18:39:17]
<thatoo> Pas avant Sun, 09 Oct 2022 05:18:22 GMT
Pas après Sat, 07 Jan 2023 05:18:21 GMT
[18:40:27]
<thatoo> Si je vais dans https://MYDOMAIN.fr/yunohost/admin/#/domains/MYDOMAIN.fr/cert-management
Yunohost me dit
> Parfait ! Vous utilisez un certificat Let’s Encrypt valide !
> Autorité de certification
> Let's Encrypt (MYDOMAIN.fr)
> Validité
> 73 jours
[18:41:56]
<thatoo> donc j'ai l'impression que le certificat let's encrypt a bien été mis à jour le Thu, 22 Dec 2022 06:19:41 GMT et est bien servi par nginx mais que le serveur de mail n'a pas été mis au courant...
[18:42:57]
<thatoo> Je ne sais vraiment pas manipuler le serveur mail et les ceetificats pour email
[19:08:54]
<tituspijean> Essaie de redémarrer le service dovecot peut-être?
[19:14:40]
<thatoo> redémarrage de dovecot ok mais pas d'amélioration
[19:15:10]
<thatoo> `openssl s_client -connect MYDOMAIN.fr:443`
et
`openssl s_client -connect MYDOMAIN.fr:587 -servername MYDOMAIN.fr -starttls smtp`
ne me retourne pas le même certificat...
[19:20:52]
<thatoo> `openssl s_client -connect MYDOMAIN.fr:443 -servername MYDOMAIN.fr`
me retourne
`Verify return code: 0 (ok)`
`openssl s_client -connect MYDOMAIN.fr:993 -servername MYDOMAIN.fr`
me retourne
`Verify return code: 0 (ok)`
mais
`openssl s_client -connect MYDOMAIN.fr:587 -servername MYDOMAIN.fr -starttls smtp`
me retourne
`Verify return code: 10 (certificate has expired)`
et
`openssl s_client -connect MYDOMAIN.fr:587 -servername MYDOMAIN.fr`
me retourne
```
CONNECTED(00000003)
140519330014528:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 303 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
```
[19:22:48]
<thatoo> au fait, dovecot, c'est pour IMAP/POP, non? mon problème est plus lié à SMTP. Je redémarre postfix du coup peut-être?
[19:25:21]
<tituspijean> Ah oui en effet
[19:26:28]
<thatoo> je viens de trouver ça dans les logs de postfix
[19:26:34]
<thatoo> `janv. 07 20:24:56 postfix/postfix-script[728022]: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ`
[19:29:52]
<thatoo> ```
janv. 07 20:24:55 postfix/postfix-script[727866]: stopping the Postfix mail system
janv. 07 20:24:55 systemd[1]: postfix@-.service: Succeeded.
janv. 07 20:24:55 systemd[1]: Stopped Postfix Mail Transport Agent (instance -).
janv. 07 20:24:55 systemd[1]: postfix@-.service: Consumed 3min 29.366s CPU time.
janv. 07 20:24:55 systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
janv. 07 20:24:56 postfix[727939]: Postfix is running with backwards-compatible default settings
janv. 07 20:24:56 postfix[727939]: See http://www.postfix.org/COMPATIBILITY_README.html for details
janv. 07 20:24:56 postfix[727939]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
janv. 07 20:24:56 postfix/postfix-script[728022]: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
janv. 07 20:24:56 postfix/postfix-script[728046]: starting the Postfix mail system
janv. 07 20:24:56 postfix/master[728048]: daemon started -- version 3.5.17, configuration /etc/postfix
janv. 07 20:24:56 systemd[1]: Started Postfix Mail Transport Agent (instance -).
```
[19:30:25]
<thatoo> I woner what is this backwards compatibility that postfix invite me to disable
[19:30:44]
<thatoo> mais bon, ça n'a rien à voir j'imagine
[19:44:44]
<thatoo> j'ai vérifié avec la commande `cat` et je confirme que
`/var/spool/postfix/etc/ssl/certs/ca-certificates.crt`
et
`/etc/ssl/certs/ca-certificates.crt`
sont différents.
Je ne sais pas si c'est normal ni pourquoi mais ils sont en effet différents.
[20:14:30]
<thatoo> est-ce qu'il existe une commande du genre `yunohost tools regen-conf certificates --force` comme pour ssh ou dnsmasq ?
[20:17:38]
<thatoo> d'après https://forum.yunohost.org/t/solved-postfix-dont-update-ssl-certificates-causing-thunderbird-email-sending-issues/19590/2, on dirait que la commande qui pourrait m'aider serait plutôt
`sudo yunohost tools regen-conf postfix --force`
[20:21:43]
<thatoo> Cette commande a en effet résolu mon problème!
[20:22:42]
<thatoo> par contre pas cool si il faut la relancer après chaque renouvellement de certificat let's encrypt....
[20:23:43]
<pti-jean> thatoo, Je viens de regarder sur mon YunoHost, et j'ai pas de /var/spool/postfix/etc/ssl/certs/ca-certificates.crt
[20:24:57]
<thatoo> Étrange
[20:29:13]
<pti-jean> Peut-être faire le test de déplacer ailleurs le fichier /var/spool/postfix/etc/ssl/certs/ca-certificates.crt ... redémarrer postfix... et refaire un test !??
[20:31:42]
<thatoo> Pour aujourd'hui, c'est bon puisque la commande `sudo yunohost tools regen-conf postfix --force` a résolu le problème.
On verra dans 73 jours quand le certificat Let's encrypt expirera si ça recommence ou pas
[20:32:18]
<pti-jean> 👍️
[22:21:22]
<denis> hi
[22:21:33]
<denis> is anyone here
[22:21:58]
<Guest7637> #yunohost:libera.chat
[22:23:57]
<Guest7637> i cant add certificate to yunohost
[22:24:11]
<Guest7637> it says something about diagnose
[22:24:12]
<Guest7637> when i run it
[22:24:20]
<Guest7637> theres nothing related to dns and web
[22:24:24]
<Guest7637> please help
[22:57:33]
<rathantara> run a diagnose test first and then add lets encrypt cert (green button)