[00:06:42]
<Gwên> Bonsoir :) Est-ce qu'on pourra bientôt mettre à jour Conduit en 0.10.11 ? Il y a une vulnérabilité importante corrigée ^^
[00:09:52]
<Aleks (he/him/il/lui)> il y a une PR automagique qui a été créée par le bot, les tests semblent ok mais je ne sais pas qui s'occupe traditionellement de cette app pour merger etc : https://github.com/YunoHost-Apps/conduit_ynh/pull/62
[01:09:16]
<m606> il n'y a personne de dédié à cette app manifestement. Je l'ai fait la dernière fois et cette fois-ci, mais ne l'utiilisant pas moi-même, je ne suis pas la personne la mieux placée.
[01:17:01]
<m606> Et pour info, le repo upstream ne fournit que les sources avec la release mais précompile les binaires dans un job Gitlab lié, dont il faut copier les URLs de téléchargement à la main pour les mettre à jour dans le manifeste (l'URL des binaires contient le numéro du job qui n'est pas prévisible). L'autoupdater de YNH a tout de même été configuré pour cette app afin de recevoir les notifications des nouvelles versions dans le repo du paquet, mais la fusionner telle quelle sans autre modification ne changerait rien concrètement (binaires précédentes avec simplement numéro de version dans le manifeste modifié) - le CI est trompeur ici en quelque sorte (=cela fonctionne, mais ce n'est pas la version annoncée).
[12:53:57]
<Chatpitaine Caverne> Did you manage to go through that ?
[12:54:09]
<everlastingos> no
[12:54:17]
<everlastingos> so need help plz
[12:54:41]
<everlastingos> did copy all the config from a new install /etc/fail2ban
[12:54:59]
<everlastingos> but do now get error :
sudo cat /var/log/fail2ban.log
2026-01-01 21:49:31,744 fail2ban.server [151795]: INFO --------------------------------------------------
2026-01-01 21:49:31,744 fail2ban.server [151795]: INFO Starting Fail2ban v1.0.2
2026-01-01 21:49:31,744 fail2ban.observer [151795]: INFO Observer start...
2026-01-01 21:49:31,745 fail2ban.database [151795]: INFO Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2026-01-01 21:49:31,746 fail2ban.database [151795]: WARNING New database created. Version '4'
2026-01-01 21:53:00,157 fail2ban.server [151795]: INFO Shutdown in progress...
2026-01-01 21:53:00,157 fail2ban.observer [151795]: INFO Observer stop ... try to end queue 5 seconds
2026-01-01 21:53:00,177 fail2ban.observer [151795]: INFO Observer stopped, 0 events remaining.
2026-01-01 21:53:00,218 fail2ban.server [151795]: INFO Stopping all jails
2026-01-01 21:53:00,218 fail2ban.database [151795]: INFO Connection to database closed.
2026-01-01 21:53:00,218 fail2ban.server [151795]: INFO Exiting Fail2ban
2026-01-01 22:01:38,440 fail2ban.server [152929]: INFO --------------------------------------------------
2026-01-01 22:01:38,440 fail2ban.server [152929]: INFO Starting Fail2ban v1.0.2
2026-01-01 22:01:38,441 fail2ban.observer [152929]: INFO Observer start...
2026-01-01 22:01:38,445 fail2ban.database [152929]: INFO Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2026-01-01 22:01:38,446 fail2ban.database [152929]: WARNING New database created. Version '4'
2026-01-01 22:01:38,446 fail2ban.transmitter [152929]: ERROR Command ['server-stream', [['set', 'syslogsocket', 'auto'], ['set', 'loglevel', 'INFO'], ['set', 'logtarget', '/var/log/fail2ban.log'], ['set', 'allowipv6', 'auto'], ['set', 'dbfile', '/var/lib/fail2ban/fail2ban.sqlite3'], ['set', 'dbmaxmatches', None], ['set', 'dbpurgeage', '1d']]] has failed. Received TypeError("int() argument must be a string, a bytes-like object or a real number, not 'NoneType'")
2026-01-01 22:01:38,447 fail2ban [152929]: ERROR NOK: ("int() argument must be a string, a bytes-like object or a real number, not 'NoneType'",)
2026-01-01 22:01:38,447 fail2ban.server [152929]: INFO Shutdown in progress...
2026-01-01 22:01:38,447 fail2ban.observer [152929]: INFO Observer stop ... try to end queue 5 seconds
2026-01-01 22:01:38,467 fail2ban.observer [152929]: INFO Observer stopped, 0 events remaining.
2026-01-01 22:01:38,507 fail2ban.server [152929]: INFO Stopping all jails
2026-01-01 22:01:38,507 fail2ban.database [152929]: INFO Connection to database closed.
2026-01-01 22:01:38,708 fail2ban.server [152929]: INFO Exiting Fail2ban
[12:57:17]
<Chatpitaine Caverne> Do you have a not too old backup of the system part ? So you could untar it somewhere and then copy fail2ban files in place.
[13:00:58]
<Chatpitaine Caverne> Well I looked in mine and it seems /etc/fail2ban etc are not in there.
[13:12:53]
<Chatpitaine Caverne> everlastingos: here is the content of my fail2ban service status : https://paste.yunohost.org/raw/wananulaxu
And the content of `/etc/systemd/system/fail2ban.service.d/systemd-override-bind-nftables.conf`
```
/etc/systemd/system/fail2ban.service.d # cat systemd-override-bind-nftables.conf
# This override config restarts and reloads fail2ban when nftables is started/reloaded
[Unit]
PartOf=nftables.service
ReloadPropagatedFrom=nftables.service
```
In case it helps.
[13:15:28]
<Chatpitaine Caverne> And the content of `/lib/systemd/system/fail2ban.service`
```
[Unit]
Description=Fail2Ban Service
Documentation=man:fail2ban(1)
After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service
PartOf=firewalld.service
[Service]
Type=simple
Environment="PYTHONNOUSERSITE=1"
ExecStart=/usr/bin/fail2ban-server -xf start
# if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local
# ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start
ExecStop=/usr/bin/fail2ban-client stop
ExecReload=/usr/bin/fail2ban-client reload
RuntimeDirectory=fail2ban
PIDFile=/run/fail2ban/fail2ban.pid
Restart=on-failure
RestartPreventExitStatus=0 255
Environment="PYTHONNOUSERSITE=yes"
[Install]
WantedBy=multi-user.target
```
[13:24:09]
<Chatpitaine Caverne> everlastingos: And another point, if you copied from a fresh install of yunohost, was it the same release of yunohost as yours ?
[13:26:28]
<otm33> everlastingos: Can you check the value of dbmaxmatches in /etc/fail2ban/fail2ban.conf ? It should be an integer -the default one is 10- not 'None'
[13:28:23]
<otm33> *a string converted to int
[13:35:43]
<otm33> It seems to be empty in your conf file.
[20:34:50]
<Gwên> Hello
[20:34:58]
<Gwên> Un petit besoin d'aide avec Writefreely
[20:35:14]
<Gwên> J'ai activé le suivi par mail mais quand quelqu'un essaie de s'abonner par ce biais, il a juste une erreur serveur
[20:36:31]
<Gwên> D'autant plus bizarre : malgré l'erreur serveur, le site indique qu'on est bien abonné à la newsletter, mais son mail n'apparaît pas dans la liste des abonnés par mail...
[20:42:40]
<@plumf:epider.me> > <@gwen:grtt.fr> J'ai activé le suivi par mail mais quand quelqu'un essaie de s'abonner par ce biais, il a juste une erreur serveur
je penses qu'il faut plus d'informations sur l'erreur, et des informations technique. Mais je ne sais pas comment avoir accès aux logs/journaux specifiquement de Writefreely... qui pourrait peut etre t'indiquer l'erreur.
[20:45:53]
<Gwên> J'ai ça en dernier :
janv. 02 21:35:35 writefreely[425968]: ERROR: 2026/01/02 21:35:35 email.go:155: Failed to send subscription confirmation email: Mail Error on STARTTLS: tls: failed to verify certificate: x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs
[21:14:28]
<trendless> there's an issue with the default config; I'll push an update to the repo, but in the meantime you can edit /var/www/writefreely/config.ini and change `smtp_enable_start_tls` to `false` and see if it fixes it.
[21:16:40]
<Gwên> > <@trendless:zeroes.ca> there's an issue with the default config; I'll push an update to the repo, but in the meantime you can edit /var/www/writefreely/config.ini and change `smtp_enable_start_tls` to `false` and see if it fixes it.
Thank you!
[21:16:45]
<Gwên> Gonna try
[21:26:54]
<Gwên> Made things worse ^^'
[21:27:26]
<Gwên> Nope, still doesn't work :/
[21:27:42]
<Gwên> I guess I'll have to wait for the update, sorry! ^^
[21:33:32]
<trendless> Gwên: oh, did you restart the writefreely service after changing the config.ini?
[21:35:06]
<Gwên> > <@trendless:zeroes.ca> Gwên: oh, did you restart the writefreely service after changing the config.ini?
...
[21:35:09]
<Gwên> I
[21:35:11]
<Gwên> am
[21:35:12]
<Gwên> DUMB
[21:35:20]
<trendless> I forgot to mention that; sorry!
[21:35:57]
<Gwên> Doing it rn
[21:39:37]
<Gwên> It works! Thank you!
[21:43:06]
<Gwên> Little problem remaining: don't know why but when you click to subscrire with a mail, it leads you to a "page not found". It does send the confirmation mail and it works after that but it's strange Oo
[21:45:28]
<trendless> that *is* a bit strange 🤔
[21:49:06]
<trendless> Are there any relevant entries in the writefreely, nginx/access, nginx/$yourdomain-access, or nginx/$yourdomain-error logs?
[22:54:07]
<Gwên> Nope :/
[22:54:10]
<Gwên> Just checked the logs, there's nothing
[22:54:59]
<Gwên> Maybe I need to create the page xD
[23:04:00]
<Gwên> Yep, that's it
[23:04:12]
<Gwên> It redirected to a page that didn't exist yet, so I created the page
[23:04:21]
<Gwên> That's a bit convoluted but it worked