[02:48:59]
<carrabelloy[m]> I can't get my fail2ban to work. Have done everything. Still does not want to, I get really angry and I do not know what this is 🤬
```
root@darknight-coffee /home/carrabelloy # sudo fail2ban-client -d
2023-03-30 02:45:08,832 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,832 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban [176946]: ERROR Failed during configuration: Bad value substitution: option 'backend' in section 'sshd' contains an interpolation key 'sshd_backend' which is not a valid option name. Raw value: '%(sshd_backend)s'
ERROR: The configuration stream failed because of the invalid syntax.
2023-03-30 02:45:08,837 fail2ban [176946]: ERROR Init of command line failed
root@darknight-coffee /home/carrabelloy #
```
[03:32:11]
<carrabelloy[m]> * ```
# sudo fail2ban-client test
2023-03-29 22:51:53,690 fail2ban.configreader \[132201\]: ERROR No section: 'Definition'
2023-03-29 22:51:53,690 fail2ban.configreader \[132201\]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader \[132201\]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader \[132201\]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader \[132201\]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban \[132201\]: ERROR Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?
root@............................ /.............. # sudo nano /etc/fail2ban/jail.conf
root@................................... /home/.......................... #
The problem is that it is a day later. They are probably sytag errors but I still do not know where. Although I set the log level to Dubag to learn more. In addition, I am every area through geagngen again. in these areas have # sudo grep -rl "\[definition\]" /etc/fail2ban/filter.d/ /etc/fail2ban/filter.d/yunohost.conf /etc/fail2ban/filter.d/postfix-sasl.conf /etc/fail2ban/filter.d/postfix-sasl.local root@darknight-coffee /home/..........# /etc/fail2ban/filter.d/yunohost.conf /etc/fail2ban/filter.d/postfix-sasl.conf /etc/fail2ban/filter.d/postfix-sasl.local root@............... /home/........ # don't know where the error is or points me out like to use a color Unkt or so. Can anyone give me a tip. or help. Or are there ready-made jails? Thanks if answer comes.
```
[03:34:46]
<carrabelloy[m]> * I can't get my fail2ban to work. Have done everything. Still does not want to, I get really angry and I do not know what this is 🤬
```
root@..................../home/.............. # sudo fail2ban-client -d
2023-03-30 02:45:08,832 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,832 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,833 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban.configreader [176946]: ERROR No section: 'Definition'
2023-03-30 02:45:08,837 fail2ban [176946]: ERROR Failed during configuration: Bad value substitution: option 'backend' in section 'sshd' contains an interpolation key 'sshd_backend' which is not a valid option name. Raw value: '%(sshd_backend)s'
ERROR: The configuration stream failed because of the invalid syntax.
2023-03-30 02:45:08,837 fail2ban [176946]: ERROR Init of command line failed
root@................... /home/..................... #
```
[05:03:23]
<tituspijean> carrabelloy[m]: I cannot help you much more, but try `sudo yunohost tools regen-conf fail2ban -f`
[05:07:06]
<carrabelloy[m]> > <@titus[m]:libera.chat> carrabelloy[m]: I cannot help you much more, but try `sudo yunohost tools regen-conf fail2ban -f`
thank `The error indicates a problem with the substitution of the __prefix_line key in the prefregex option. It seems that __prefix_line is not defined. To fix this problem we can try to import the definition of __prefix_line from another file.`
[06:39:46]
<olivier[m]> version de? cryptpad? dans l'ensemble, je suis assez régulier sur mes montées de version, donc sauf si tu as enchainé plusieurs versions en quelques jours, j'ai du passer par tous les intermédiaires
[06:51:59]
<carrabelloy[m]> > <@titus[m]:libera.chat> carrabelloy[m]: I cannot help you much more, but try `sudo yunohost tools regen-conf fail2ban -f`
```
root@darknight-coffee /etc/fail2ban/filter.d # sudo systemctl status fail2ban
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2023-03-30 06:45:11 UTC; 5min ago
Docs: man:fail2ban(1)
Process: 215347 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
Process: 215430 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
Process: 215431 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
Main PID: 215431 (code=exited, status=255/EXCEPTION)
CPU: 80ms
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban [215431]: ERROR Failed during configuration: Bad value s>
Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,490 fail2ban [215431]: ERROR Async configuration of server failed
Mar 30 06:45:11 darknight-coffee.org systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
Mar 30 06:45:11 darknight-coffee.org systemd[1]: fail2ban.service: Failed with result 'exit-code'.
```
[06:55:17]
<carrabelloy[m]> what i don't understand about the whole thing is why mal built this into the system. Otherwise I could have uninstalled it and would have played it again. If I have bad luck I now have to rebuild everything. That must not be true. Really thanks for the tip.
[08:38:10]
<Luis_> Hello everyone
[09:39:28]
<Westbam> Salut, des utilisateurs de seafile sous yunohost par ici ?? je l'ai installé hier. Le client web fonctionne très bien, par contre je n'arrive pas a me connecter dessus en passant par un client lourd (android, mac ou windows) j'ai vu un vieux ticket sur le github https://github.com/YunoHost-Apps/seafile_ynh/issues/100 mais il n'y a pas eu de réponse. c'est bug ou un souci de conf ?
[09:44:51]
<Westbam> ON est d'accord qu'il faut bien passé par "Authentification unique" pour se connecter
[10:35:37]
<Ryan> > <@pavezzi:libera.chat> but thank you Aleks (he/him/il/lui), got it fixed with: yunohost user group add-mailalias admins abuse@domain.tld
I noticed weird issues with mail after a recent update. I'll check out the release notes for 11.1. My issue is I was getting "undelivered mail" errors to admin@ (expanded from root@), but mail is still bring delivered, which seemed odd. So I was getting 2 emails: one was the expected email and the other was a mail daemon email saying it COULDNT be delivered. I'll check out this add alias command.
[11:01:27]
<carrabelloy[m]> > ```
> root@darknight-coffee /etc/fail2ban/filter.d # sudo systemctl status fail2ban
> ● fail2ban.service - Fail2Ban Service
> Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
> Active: failed (Result: exit-code) since Thu 2023-03-30 06:45:11 UTC; 5min ago
> Docs: man:fail2ban(1)
> Process: 215347 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
> Process: 215430 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
> Process: 215431 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
> Main PID: 215431 (code=exited, status=255/EXCEPTION)
> CPU: 80ms
>
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban.configreader [215431]: ERROR No section: 'Definition'
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,489 fail2ban [215431]: ERROR Failed during configuration: Bad value s>
> Mar 30 06:45:11 darknight-coffee.org fail2ban-server[215431]: 2023-03-30 06:45:11,490 fail2ban [215431]: ERROR Async configuration of server failed
> Mar 30 06:45:11 darknight-coffee.org systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
> Mar 30 06:45:11 darknight-coffee.org systemd[1]: fail2ban.service: Failed with result 'exit-code'.
> ```
he /etc/fail2ban/filter.d/nextcloud.conf file appears to be the problem. You should check this file and make sure that it contains the [definition] section.
[11:10:14]
<carrabelloy[m]> ```
[Definition]
failregex = ^{"reqId":".*","level":2,"time":".*","remoteAddr":"<HOST>","user":".*","app":"core","method":".*","url":".*","message":"Login failed: '.*' \(Remote IP: '<HOST>'\)$
^{"reqId":".*","level":2,"time":".*","remoteAddr":"<HOST>","user":".*","app":"core","method":".*","url":".*","message":"Login failed: '.*' \(Remote IP: '<HOST>'\)","userAgent":".*","version":".*"$
^{"reqId":".*","level":2,"time":".*","remoteAddr":"<HOST>","user":".*","app":"core","method":".*","url":".*","message":"Login failed: '.*' \(Remote IP: '<HOST>'\)","userAgent":".*","version":".*","id":".*"$
ignoreregex =
```
[11:10:36]
<carrabelloy[m]> > root@darknight-coffee /etc/fail2ban/filter.d # sudo systemctl status fail2ban
> ● fail2ban.service - Fail2Ban Service
> Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
> Active: failed (Result: exit-code) since Thu 2023-03-30 10:47:25 UTC; 56s ago
> Docs: man:fail2ban(1)
> Process: 253372 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
> Process: 253382 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
> Process: 253383 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
> Main PID: 253383 (code=exited, status=255/EXCEPTION)
> CPU: 96ms
>
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban.configreader [253383]: ERROR No section: 'Definition'
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,604 fail2ban [253383]: ERROR Failed during configuration: >
> Mar 30 10:47:25 darknight-coffee.org fail2ban-server[253383]: 2023-03-30 10:47:25,605 fail2ban [253383]: ERROR Async configuration of server>
> Mar 30 10:47:25 darknight-coffee.org systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
> Mar 30 10:47:25 darknight-coffee.org systemd[1]: fail2ban.service: Failed with result 'exit-code'.
[11:12:30]
<carrabelloy[m]> Would anyone have an idea what else this could be please ?
[12:05:54]
<coffeehacko[m]> Salut ! Désolé, je vais parler français car mon anglais est très mauvais
[12:06:15]
<coffeehacko[m]> J'ai un gros problème avec Moodle dans Tor
[12:06:23]
<coffeehacko[m]> j'ai ouvert un ticket sur github à ce sujet
[12:07:54]
<coffeehacko[m]> Moodle fonctionne correctement sur le web de surface mais pas dans Tor, le navigateur Tor n'arrive pas à se connecter à l'adresse en .onion sur laquelle est installée Moodle
[12:09:02]
<coffeehacko[m]> les entêtes http du site en .onion indiquent ""HTTP/1.1 303 See Other"
[13:30:03]
<lautre> Pas de soucis pour causer en Français.
[13:31:10]
<lautre> J'ai remarqué qu'il fallait autoriser les référer dans le navigateur si l'application n'a pas un accès publique
[13:33:05]
<lautre> Je ne sais pas comment le navigateur tor protège et filtre les informations.
Il faudrait tester voir si d'autres applications fonctionnement, c'est a dire d'autres trucs que moodle
[13:33:40]
<lautre> Histoire de savoir si c'est spécifique à Moodle
[14:00:14]
<coffeehacko[m]> > <@lautre[m]:libera.chat> Pas de soucis pour causer en Français.
D'autre applications fonctionnent correctement dans Tor en .onion, ça ne le fait qu'avec Moodle
[15:10:59]
<lautre> Il n'y a plus qu'à attendre que quelqu'un ait des pistes
[16:58:14]
<rodinux> Bonjour, j'ai des soucis pour restaurer une application cryptpad à force de devoir réinstaller un certificat let'sencrypt, j'ai dépassé une limite !! Un massage dit d'attendre pour réssayer demain après une heure tard le soir.... On peut contourner cela ?
[17:00:48]
<Guillaume Bouzige> non, j'ai eu le cas plein de fois
[17:01:15]
<Guillaume Bouzige> soit tu change de domaine si tu es presser soit tu attends
[17:01:45]
<rodinux> Ok, mon problème c'est que c'est une restauration donc, je vais être obligé d'attendre...
[17:02:33]
<Guillaume Bouzige> alors oui
[17:02:34]
<rodinux> la date qui'il propose j'imagine: 'type': 'urn:ietf:params:acme:error:rateLimited', 'detail': 'Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: sandbox-cryptpad.domain.tld, retry after 2023-03-31T19:45:10Z: see https://letsencrypt.org/docs/duplicate-certificate-limit/', 'status': 429
[17:03:11]
<Guillaume Bouzige> yeah jai eut la mm pendant mes tests...
[17:03:30]
<Guillaume Bouzige> du coup maintenant jai deux domaines de test
[17:04:27]
<Guillaume Bouzige> tu peut acheter des domaines de test pour qq euros par an
[17:05:56]
<rodinux> Je me demandais si en changeant le certificat auto-signé, cela résoudrait, mais peut-être que au contraire !!
[17:07:25]
<rodinux> Et peut-être que c'est juste le nom de domaine qui compte... je vais attendre, si demain ça passe pour sauver des sonnées au moins
[17:08:26]
<Guillaume Bouzige> tu devrai plutot avoir une genre de pre-prod ou tu peut test tes updates avant sur un domaine de test avant de deployer tes updates sur ta prod...
[17:08:42]
<Guillaume Bouzige> comme ca tes peinard...
[17:11:55]
<Guillaume Bouzige> genre un VPS scaleway a 0.016 de l'heure ou tu monte ta sauvegarde tu fais tes tests et tu avise...
[17:12:22]
<rodinux> Je fais cela un peu avec un autre serveur, mais il y a eu beaucoup de petits soucis avec cryptpad et j'ai du trop souvent remove et restore à chaque fois il doit créer un sous-domaine qui est supprimer avec le remove et où il faut ajouter le ssl
[17:12:33]
<rodinux> De plus, je compte faire une réinstallation plus propre maintenant que j'ai bien compris, mais sur un autre sous-domaine pour ne pas avoir ce problème...
[17:13:41]
<Guillaume Bouzige> oui mais sous domaine ca suffit pas il te faut un domaine
[17:13:50]
<rodinux> Mais oui, plus je me confronte à des soucis, plus je réfléchi à ne pas aller trop vite et à test test test test avant, je consens
[17:15:04]
<Guillaume Bouzige> desole pour les ratés sur les updates mais ont fait au mieux...hesite pas a me solliciter si tu as besoin
[17:15:17]
<rodinux> un domaine je voulais dire... j'ai tester une installation fraîche sur un autre domaine, d'ailleurs une question
[17:16:02]
<Guillaume Bouzige> ok, azy
[17:16:16]
<rodinux> est-ce que je peux ajouter une phrase dans le main.js pour le Salt avant de créer le prmier utilisateur ?
[17:17:03]
<rodinux> https://docs.cryptpad.org/en/admin_guide/customization.html#security-hardening
[17:17:35]
<Guillaume Bouzige> je pense que oui
[17:18:27]
<Guillaume Bouzige> vu que la gestion des utilisateurs es faites par cryptpad et non yunohost
[17:18:39]
<Guillaume Bouzige> mais j'ai pas tester...
[17:18:48]
<Guillaume Bouzige> 🤓
[17:19:07]
<rodinux> Je testerai... pas sur la prod...
[17:19:53]
<Guillaume Bouzige> 👍
[17:20:05]
<rodinux> Et si ça fonctionne, je réinstallerai une instance propre avec ce petit plus...
[17:20:52]
<Guillaume Bouzige> cool hesite pas a partager ca dans la page dediee a cryptpad sur le forum
[17:21:45]
<Guillaume Bouzige> j'ai encore du boulot sur cryptpad pour reparer la restauration et le changement d'url qui sont je pense encore bien peter
[17:22:46]
<rodinux> Oui, peut-être que l'on peut même envisager un random key qui viendrait en post-install s'ajouter....
[17:24:29]
<rodinux> secret_key=$(ynh_string_random --length=25)
[17:24:45]
<Guillaume Bouzige> why not
[17:26:07]
<Guillaume Bouzige> fait une issue comme ca on oublie pas...
[17:26:16]
<Guillaume Bouzige> stp
[17:28:34]
<Guillaume Bouzige> mais test d'abord si ca marche avant...
[18:15:36]
<rodinux> en tous les cas merci Guillaume Bouzige pour tout ce boulot, je t'en suis reconnaissant et à tous les contributeurs..;
[18:44:14]
<GuillaumeL> Hello
[18:44:33]
<GuillaumeL> I'm trying to update my yunohost serveur
[18:44:43]
<GuillaumeL> I get this messages
[18:44:46]
<GuillaumeL> W:
[18:44:46]
<GuillaumeL> GPG error: https://packages.sury.org/php bullseye InRelease: The
[18:44:47]
<GuillaumeL> available: NO_PUBKEY B188E2B695BD4743
[18:44:47]
<GuillaumeL> following signatures couldn't be verified because the public key is not
[18:44:56]
<GuillaumeL> E: The repository 'https://packages.sury.org/php bullseye InRelease' is not signed.
[18:45:32]
<GuillaumeL> In root, I thought I could pass these commands
[18:45:35]
<GuillaumeL> apt-key del B188E2B695BD4743
[18:45:43]
<GuillaumeL> apt-key add https://packages.sury.org/php/apt.gpg
[18:46:03]
<GuillaumeL> The 1st one said OK
[18:46:11]
<GuillaumeL> But the 2nd one said
[18:46:18]
<GuillaumeL> gpg: impossible d'ouvrir « https://packages.sury.org/php/apt.gpg » : Aucun fichier ou dossier de ce type
[18:46:41]
<GuillaumeL> eg no apt.gpg file
[18:47:41]
<GuillaumeL> But I see this file with my browser
[18:47:56]
<GuillaumeL> What's wrong ?
[18:48:04]
<rodinux> sudo wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg
[18:48:54]
<rodinux> sudo wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg
[18:49:05]
<rodinux> ??
[18:49:44]
<GuillaumeL> Great :-)
[18:50:06]
<rodinux> 😀
[18:50:12]
<GuillaumeL> Thank you rodinux
[18:50:24]
<rodinux> 🤪
[18:51:35]
<rodinux> I beleive now All machines are broken...
[18:53:49]
<GuillaumeL> WARNING - E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».
[18:54:18]
<GuillaumeL> You've already been through this issue ?
[18:55:34]
<rodinux> I think so, I have to remember... What version of Yunohost you are upgrading ?
[18:55:51]
<GuillaumeL> WARNING - Impossible de mettre à jour les paquets suivants :...
[18:56:25]
<GuillaumeL> followed by a full page of package names
[18:57:26]
<rodinux> Are you upgrading a buster version ?
[18:59:33]
<GuillaumeL> buster ? What is this ?
[19:00:32]
<rodinux> what returns `yunohost tools versions`
[19:01:01]
<GuillaumeL> ❯ yunohost tools versions
[19:01:02]
<GuillaumeL> yunohost:
[19:01:02]
<GuillaumeL> ─╯
[19:01:03]
<GuillaumeL> repo: stable
[19:01:04]
<GuillaumeL> repo: stable
[19:01:04]
<GuillaumeL> version: 4.4.2.6
[19:01:04]
<GuillaumeL> yunohost-admin:
[19:01:05]
<GuillaumeL> version: 4.4.1
[19:01:07]
<GuillaumeL> moulinette:
[19:01:08]
<GuillaumeL> repo: stable
[19:01:08]
<GuillaumeL> repo: stable
[19:01:08]
<GuillaumeL> ssowat:
[19:01:08]
<GuillaumeL> version: 4.4.1
[19:01:09]
<GuillaumeL> version: 4.4.1
[19:01:27]
<GuillaumeL> I use debian bullseye
[19:01:55]
<rodinux> Buster was Debian 10, so yes you are on a Debian 10 Buster version it is not bullseye
[19:03:10]
<GuillaumeL> OS: Debian GNU/Linux 10 (buster) x86_64
[19:03:18]
<GuillaumeL> You're right
[19:03:29]
<rodinux> bullseye begin with 11.*
[19:04:08]
<rodinux> It is a big update https://forum.yunohost.org/t/yunohost-11-1-release-sortie-de-yunohost-11-1/23378/69
[19:04:15]
<Guillaume Bouzige> you should not use apt to do such upgrade but instead use the migration feature of yunohost...
[19:04:25]
<GuillaumeL> Should I update debian first ?
[19:05:14]
<rodinux> no, just a minute, you first need arrive at the last buster yubohost version
[19:05:38]
<rodinux> sudo yunohost tools update
[19:05:50]
<Aleks (he/him/il/lui)> You should follow Yunohost migration procedure and not manually tweak apt ...
[19:06:59]
<rodinux> https://forum.yunohost.org/t/yunohost-11-1-release-sortie-de-yunohost-11-1/23378#fr-version-franaise-13
[19:07:35]
<rodinux> de rien
[19:07:40]
<GuillaumeL> With `sudo yunohost tools update` I get a list of 900 packages
[19:10:01]
<rodinux> peut-être que tu auras des soucis suivant les apps... mais toute façon il faut y aller...
[19:10:34]
<GuillaumeL> Du coup je ne saisis pas ce que je dois faire là
[19:11:07]
<rodinux> yunohost tools upgrade system
[19:12:26]
<rodinux> il faut privilégier la moulinette et les commandes yunohost sur cet environnement !
[19:12:53]
<GuillaumeL> J'ai lancé la commande, et je me retrouve avec ce warning : "Impossible de mettre à jour les paquets suivants" suivi d'une liste de 900 paquets
[19:13:12]
<GuillaumeL> Sans plus d'info sur ce qui bloque
[19:13:39]
<rodinux> sudo yunohost upgrade app
[19:14:51]
<GuillaumeL> J'ai trouvé un message me disant qu'une migration était en attente
[19:15:06]
<GuillaumeL> Je vient de la lancer via l'interface admin
[19:15:28]
<GuillaumeL> Pour l'instant, ça tourne
[19:15:46]
<rodinux> ok la migration !
[19:16:27]
<rodinux> ça va prendre du temps, il a peut-être des choses qui ne fonctionneront pas tout de suite après...
[19:16:43]
<GuillaumeL> ok
[19:18:34]
<rodinux> à la fin, il y aura peut-être ancore une migration pour python3, pour postgresql, c'est parfois un peu chaud, il faudra forcer des upgrade d'app `yunohost app upgrade mon_app -F` parfois
[19:20:00]
<rodinux> Et ensuite il faut configurer ton nouvel administrateur, le premier utilisateur pour qu'il puisse se connecter en .ssh car l'utilisateur admin doit disparaître...
[19:20:56]
<rodinux> Que quand tu es sûr d'avoir bien mis en place tes droits avec le nouvel utilisateur admin
[19:22:27]
<GuillaumeL> Je vois
[19:36:14]
<rodinux> patiente... ☕️
[19:37:17]
<GuillaumeL> Bonne idée le :coffee:
[19:37:18]
<GuillaumeL> Bonne idée le :coffee:
[19:54:11]
<Weiming> Hi all. I have a general question about Yunohost. If I install the NextCloud instance with Yuno, does it also handle the upgrade for PHP?
[19:54:28]
<Weiming> Thank you.
[19:55:21]
<Aleks (he/him/il/lui)> yes, though it's not clear what you mean by "handle the upgrade for PHP"
[19:56:13]
<Weiming> Thank you. For example, if I installed the NextCloud instance today, presumably the PHP version is going to be today's version. In a year when I upgrade NextCloud, does Yunohost also upgrade my system PHP version.
[19:57:18]
<Weiming> Right now I install NextCloud manually on a raspberry pi. I have to manually upgrade PHP which has not been my favorite part of self hosting.
[19:58:46]
<rodinux> also, yunohost simplify a lot, but it is better to be attentive and upgrade frequently, rather than wait a year
[20:00:46]
<Weiming> Thanks!
[20:09:41]
<Aleks (he/him/il/lui)> > <@Weiming:libera.chat> Right now I install NextCloud manually on a raspberry pi. I have to manually upgrade PHP which has not been my favorite part of self hosting.
well basically yunohost takes care of this automagically yes
[20:10:43]
<Aleks (he/him/il/lui)> the rule of thumb is "if it's boring technical stuff, yunohost should take care of it, and if it does not, this should be thought of as a bug"
[21:58:34]
<craigvb[m]> Is it possible to block an IP address in the yunohost firewall?
[22:01:00]
<Aleks (he/him/il/lui)> Nope
[22:05:11]
<craigvb[m]> having a weird issue where I can't access any sites or email from my internet connection but I can ping the sites... If I use a vpn, proxy, cell data rather than my ISP connection everything works fine and everything was working fine on it until 2 days ago. Other's on same ISP can access (starlink) so can't for the life of me figure out what's going on
[23:30:30]
<coffeehacko[m]> J'ai trouvé la solution pour mon problème avec Moodle dans Tor en .onion https://github.com/YunoHost-Apps/moodle_ynh/issues/82