Thursday, February 12, 2026
support@conference.yunohost.org
February
Mon Tue Wed Thu Fri Sat Sun
            1
2
3
4
5
6
7
8
9
10
11
12
13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28  
             

[00:13:38] <Chatpitaine Caverne> Fritjof (backupkonto): Forget about the upgrade log, I read the scripts, it's clearly the same issue as restore after fail.
[00:42:07] <Linux in a Bit> This started a few days ago, and I haven't been able to access any apps, all of which I host on .local domains, but the webadmin page loads perfectly fine.
Right now I can run `sudo systemctl restart yunomdns` every time the server restarts, but that's not ideal, especially when I'm not around to do it.
[00:55:02] <Linux in a Bit> I don't know why, but `yunomdns` won't start properly after a server restart:
```
neurodb_admin@neurodb:~$ sudo systemctl status yunomdns
[sudo] password for neurodb_admin:
● yunomdns.service - YunoHost mDNS service
Loaded: loaded (/etc/systemd/system/yunomdns.service; enabled; preset: enabled)
Active: active (running) since Wed 2026-02-11 18:27:12 CST; 1min 18s ago
Main PID: 673 (python3)
Tasks: 1 (limit: 18846)
Memory: 15.9M
CPU: 115ms
CGroup: /system.slice/yunomdns.service
└─673 python3 /usr/bin/yunomdns

Feb 11 18:27:12 neurodb.local systemd[1]: Started yunomdns.service - YunoHost mDNS service.
Feb 11 18:27:14 neurodb.local yunomdns[673]: Registering...
Feb 11 18:27:14 neurodb.local yunomdns[673]: Registered. Press Ctrl+C or stop service to stop.
neurodb_admin@neurodb:~$ sudo systemctl restart yunomdns
neurodb_admin@neurodb:~$ sudo systemctl status yunomdns
● yunomdns.service - YunoHost mDNS service
Loaded: loaded (/etc/systemd/system/yunomdns.service; enabled; preset: enabled)
Active: active (running) since Wed 2026-02-11 18:30:02 CST; 51s ago
Main PID: 1393 (python3)
Tasks: 2 (limit: 18846)
Memory: 13.3M
CPU: 158ms
CGroup: /system.slice/yunomdns.service
└─1393 python3 /usr/bin/yunomdns

Feb 11 18:30:02 neurodb.local systemd[1]: Started yunomdns.service - YunoHost mDNS service.
Feb 11 18:30:04 neurodb.local yunomdns[1393]: Adding <redacted>.local with addresses ['<redacted>'] on interface enp1s0
Feb 11 18:30:04 neurodb.local yunomdns[1393]: Adding <redacted>.local with addresses ['<redacted>'] on interface enp1s0
Feb 11 18:30:04 neurodb.local yunomdns[1393]: Adding <redacted>.local with addresses ['<redacted>'] on interface enp1s0
Feb 11 18:30:04 neurodb.local yunomdns[1393]: Registering...
Feb 11 18:30:06 neurodb.local yunomdns[1393]: Registered. Press Ctrl+C or stop service to stop.
neurodb_admin@neurodb:~$
```
Notice how it only shows that the addresses were added when I run it manually after boot.
I've tried `sudo yunohost tools regen-conf` already and it didn't fix the issue, and I searched the forums but found nothing much beyond that.
[00:55:52] <Linux in a Bit> This started a few days ago, possibly related to me attempting to install Vaultwarden...
I haven't been able to access any apps, all of which I host on .local domains, but the webadmin page loads perfectly fine.
Right now I can run `sudo systemctl restart yunomdns` every time the server restarts, but that's not ideal, especially when I'm not around to do it.
[07:43:04] <bbohard> Is it possible that the configuration file /etc/yunohost/mdns.yml has no "interfaces" or does not exist when yunomdns is first started ? The message "Adding…" is triggered in two loops on values in this configuration file: for each interface and for each domain.
[14:00:20] <Chatpitaine Caverne> J'ai proposé un PR : https://github.com/YunoHost-Apps/synapse_ynh/pull/608
Suis total débutant en la matière, alors à voir.
[14:58:02] <eric_G> The setuptools version is being changed in the requirements.txt file. -> https://github.com/YunoHost-Apps/synapse_ynh/pull/606/changes
[15:38:26] <Gwên> Hello
[15:38:53] <Gwên> J'ai remarqué que quand je tape www.mondomaine.fr au lieu de mondomaine.fr, j'ai une alerte de sécurité. Vous savez à quoi c'est dû ? Merci d'avance :)
[15:39:20] <Gwên> Plus précisément :
"
Connexion bloquée : problème de sécurité potentiel

LibreWolf a détecté une menace potentielle de sécurité et a interrompu le chargement de lejournaldesbriques.fr, car ce site web nécessite une connexion sécurisée.

Que pouvez-vous faire ?

lejournaldesbriques.fr a recours à une stratégie de sécurité HTTP Strict Transport Security (HSTS), une connexion sécurisée est obligatoire pour y accéder. Vous ne pouvez pas ajouter d’exception pour visiter ce site.

Le problème vient probablement du site web, vous ne pouvez donc pas y remédier. Vous pouvez le signaler aux personnes qui administrent le site."