[07:36:16]
<@everlastingos> Is there somebody that can look at the Pixelfed app on yunohost so the DM works again?
[07:41:49]
<ederto87> > <Cippr> eric_G: Bonsoir, j'ai eu un souci lors de l'upgrade de Nextcloud 31.0.8-ynh2 vers 31.0.9-ynh1 ce matin. En revanche l'upgrade est passée ce soir en ayant simplement changé la valeur du timeout du helper v2.1 de 60 à 300.
> Je ne sais pas si ça a du sens vis-à-vis de ton travail sur le `watcher.service` que j'ai vu passer sur le forum mais je souhaitais que tu aies cette information.
Je rencontre le même problème depuis quelques jours. Lors de la mise à jour un message du style "l'API de yunohost ne répond pas" apparaît et puis "la mise à jour a échoué ". Quand j'essaie de faire la MaJ à nouveau yunohost me dit qu'il y a déjà une copie de cette mise à jour faite.
Quelqu'un pourrait me donner un coup de main ?
Merci
[07:45:06]
<ederto87> https://aria.im/_bifrost/v1/media/download/AYZ43X6WWh6gPtjmh_OsKpFSWf2nSBcgtHExilOrUe5ZbOm_sLWvyUyJ_EjymFD233EK09TTPX1lK8QFY7ZM_g1CeZRy9NqQAG1hdHJpeC5vcmcvcXdJRUFzVkpNc0ZtWmtLZEFYdlVucE5v
[07:46:58]
<zhangyouyou2> 有人么
[08:17:31]
<florent> L'erreur semble indiquer qu'il existe déjà une backup "peertube-pre-upgrade2".
Tu peux essayer d'aller lister les backups et si tu la vois, la supprimer.
Ou alors lancer cette commande en SSH:
```bash
rm /home/yunohost.backup/archives/peertube-pre-upgrade2*
```
Et relancer l'upgrade
[08:22:12]
<florent> Hi,
I have used machine translation, it seems you asked whether there is anyone here.
You will probably have more answer if you talk in English here :).
Also in forums or chat, prefer asking directly your question you need to get help so you don't lose your time waiting for a first answer
[09:26:37]
<lautre> 有人。你好。
请写英文。
[09:40:57]
<ederto87> Thank you. It worked both for peertube and nextcloud. 😉
[09:41:17]
<florent> Glad to hear :)
[11:18:03]
<pherjung> Salut !
Je me rends compte que le service mDNS ne fonctionne pas comme il devrait. En effet, j'ai configuré une adresse en .local et je n'arrive pas à y accéder
[13:25:16]
<m4lvin> Two questions about the Prosody package `prosody_ynh`.
1. Should Prosody be listening on 5223 (for SSL, I think. STARTTLS works on 5222) or not? It seems it is not listening, but 5223 is included as "should be open" in the firewall tests, so I get a warning that it's not reachable.
2. Is `prosody-modules` meant to be installed? After a recent update `apt` said it is no longer needed, but for now I marked it as manually installed.
Maybe anubis knows / I saw you replying to other github issues. Wasn't sure if I should create issus for these things, so I first ask here. Big thanks for making the package!
[14:49:14]
<Melchisedech> Is anyone also having a 404 error when trying to reach https://yunohost.org or any page on that domain? (subdomains such as doc or forum don’t seem affected)
[15:52:06]
<lautre> Pas de soucis pour moi à l'instant.
[16:48:07]
<titan> Did a full upgrade today which completed successfully However I could not upgrade Prosody with the error
[16:48:20]
<titan> Warning: /var/cache/yunohost/app_tmp_work_dirs/app_0p5hjida/scripts/backup: line 13: config_path: unbound variable
Error: Failed to collect files to backed up for prosody
[17:02:49]
<Melchisedech> Ah oui, ça marche à nouveau.
[19:10:34]
<Gwên> Bonsoir :)
[19:11:03]
<Gwên> Depuis la dernière mise à jour de SearXNG j'ai des Internal Server Errors à quasi chaque requête
[19:11:15]
<Gwên> Vous savez s'il y a quelque chose que je pourrais faire ?
[19:11:27]
<Gwên> Je suis sur la dernière version de YNH avec tout à jour
[19:13:14]
<(◕‿◕) Seb (◕‿◕)> Aucun soucis sur mon instance SearXNG, également à jour.
[19:15:15]
<(◕‿◕) Seb (◕‿◕)> Tu peux tenter de relancer ton service uwsgi-app@searxng
[19:18:35]
<Gwên> J'ai changé l'url et ça semble remarcher Oo
[19:18:40]
<Gwên> Je pige pas
[19:18:41]
<Gwên> Ptete qu'il y avait trop de trafic dessus
[19:19:33]
<rodinux> j'ai un soucis avec borg qui ne veut pas se relancer...
```
2025-09-13 21:07:08,946: ERROR - Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/hook.py", line 298, in hook_callback
hook_return = hook_exec(
File "/usr/lib/python3/dist-packages/yunohost/hook.py", line 416, in hook_exec
raise YunohostError("hook_exec_failed", path=path)
yunohost.utils.error.YunohostError: Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
[19:20:09]
<Aleks (he/him/il/lui)> the fuuuuuuuuuuuuuuuuuuuuuull looooogz
[19:20:40]
<rodinux> https://paste.yunohost.org/raw/ibajizafar
[19:21:13]
<rodinux> pour cette app, mais toutes ont une erreur...
[19:21:37]
<rodinux> ```
The backup miserably failed to backup system configurations.
The backup miserably failed to backup system data.
The backup miserably failed to backup borg application.
The backup miserably failed to backup element application.
The backup miserably failed to backup grav application.
The backup miserably failed to backup nextcloud application.
The backup miserably failed to backup onlyoffice application.
The backup miserably failed to backup phpmyadmin application.
The backup miserably failed to backup redirect application.
The backup miserably failed to backup snappymail application.
The backup miserably failed to backup synapse application.
The backup miserably failed to backup wireguard application.
Creating a backup archive from the collected files…
The archive will contain about 2.9MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190650-backup_create' to get help
Creating a backup archive from the collected files…
The archive will contain about 7.2GB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190710-backup_create' to get help
Collecting files to be backed up for borg…
Declaring files to be backed up...
Backup script completed for borg. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 278.4KB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190742-backup_create' to get help
Collecting files to be backed up for element…
Declaring files to be backed up...
Backup script completed for element. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 93.9MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190758-backup_create' to get help
Collecting files to be backed up for grav…
Declaring files to be backed up...
Backup script completed for grav. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 379.1MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190814-backup_create' to get help
Collecting files to be backed up for nextcloud…
Declaring files to be backed up...
Backing up the MySQL database...
Backup script completed for nextcloud. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 15.3GB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190839-backup_create' to get help
Collecting files to be backed up for onlyoffice…
Declaring files to be backed up...
Backing up the PostgreSQL database...
Backup script completed for onlyoffice. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 31.5MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190903-backup_create' to get help
Collecting files to be backed up for phpmyadmin…
Declaring files to be backed up...
Backing up the MySQL database...
Backup script completed for phpmyadmin. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 52.2MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190922-backup_create' to get help
Collecting files to be backed up for redirect…
Backup script completed for redirect. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 48.5KB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-190942-backup_create' to get help
Collecting files to be backed up for snappymail…
Declaring files to be backed up...
Backup script completed for snappymail. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 14.8MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-191001-backup_create' to get help
Collecting files to be backed up for synapse…
Declaring files to be backed up...
Backup script completed for synapse. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 2.1GB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-191020-backup_create' to get help
Collecting files to be backed up for wireguard…
Declaring files to be backed up...
Backup script completed for wireguard. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files…
The archive will contain about 21.4MB of data.
The operation 'Create a backup archive' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250913-191100-backup_create' to get help
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
It's hightly recommended to make your backup when the service is stopped. Please stop synapse service with this command before to run the backup 'systemctl stop synapse.service'
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
Source path '' does not exist
Could not run script: /etc/yunohost/hooks.d/backup_method/05-borg_app
Custom backup method could not get past the 'backup' step
[19:21:53]
<florent> Go get the logs in `/var/log/borg/borg.log` and `/var/log/borg/<date>.log`
Unfortunately, the logs are not relevant the usual way
[19:21:56]
<florent> (something I should fix at some point)
[19:22:16]
<Aleks (he/him/il/lui)> or there's also some .err in /var/log/borg/ ?
[19:23:09]
<florent> True (I think they are usually not very useful, but let's get them as well)
[19:25:32]
<rodinux> As yesterday... an error permissions on the borg server
```
2025-09-13 21:11:16,168 INFO Creating archive at "ssh://borg@78.203.230.228:54321/~/backup::auto_wireguard-2025-09-13T21:11:12"
2025-09-13 21:11:19,413 ERROR Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/borg/remote.py", line 252, in serve
res = f(**args)
File "/usr/lib/python3/dist-packages/borg/repository.py", line 378, in get_free_nonce
with open(nonce_path) as fd:
~~~~^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: '/home/borg/backup/nonce'
2025-09-13 21:11:19,413 ERROR Borg server: Platform: Linux localhost 6.12.45-current-bcm2711 #1 SMP PREEMPT Thu Sep 11 16:45:21 UTC 2025 aarch64
Borg server: Linux: Unknown Linux
Borg server: Borg: 1.4.0 Python: CPython 3.13.5 msgpack: 1.0.3 fuse: None [pyfuse3,llfuse]
Borg server: PID: 67294 CWD: /home/borg
Borg server: sys.argv: ['/usr/bin/borg', 'serve', '--storage-quota', '50G', '--restrict-to-repository', '/home/borg/backup']
Borg server: SSH_ORIGINAL_COMMAND: 'borg serve --debug'
Platform: Linux domain.org 6.1.11-meson64 #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023 aarch64
Linux: Unknown Linux
Borg: 1.4.1 Python: CPython 3.9.2 msgpack: 1.1.0 fuse: pyfuse3 3.4.0 [pyfuse3,llfuse]
PID: 1643723 CWD: /media/data/home/yunohost.backup/tmp/auto_wireguard
sys.argv: ['/var/www/borg/venv/bin/borg', 'create', '--exclude-if-present', '.nobackup', '--stats', '::auto_wireguard-{now}', '.']
SSH_ORIGINAL_COMMAND: None
[19:26:17]
<Aleks (he/him/il/lui)> mokay so let's look at `namei -l /home/borg/backup/nonce` ?
[19:26:51]
<rodinux> on the borg server... I look first if I can connect to it by ssh...
[19:33:19]
<florent> Yeah, sounds like an rights issue like the last time.
[19:34:03]
<florent> Have you changed the `command=` part in the `authorized_keys` like I suggested the last time?
[19:34:48]
<rodinux> is a bit difficult, I am asking to groot if he can join us... borg server is on his hands...
[19:36:39]
<florent> Also answer to Aleks (he/him/il/lui)' question would be useful too
[19:38:16]
<rodinux> Soooo, yesterday I remember we must `chown borg:` the file `/home/borg/backup/config` and then I could look on the archives with `borg list`... but in the borg server the ssh is restricted by the `command=` so I can't connect ont the borg server...
[19:53:42]
<rodinux> well, must be perhaps too late for him, see later...
[19:55:28]
<florent> Probably `chown -R borg: /home/borg/backup` to fully change the folder and its descendents.
[20:48:06]
<M1k3> Bonsoir à tous. Je viens de me rendre compte d'un souci sur mon serveur YunoHost (VPS). Je ne reçois plus aucun mail et je ne peux pas en envoyer. Je ne suis pas capable de dire depuis quand cela dure. Lorsque j'essaie d'en envoyer depuis Roundcube, j'obtiens le message "Erreur SMTP 451".
[20:49:38]
<Aleks (he/him/il/lui)> est-ce que `yunohost tools regen-conf postfix --dry-run` raconte des choses
[20:51:53]
<M1k3> > <@Alekswag:matrix.org> est-ce que `yunohost tools regen-conf postfix --dry-run` raconte des choses
Yes :
```
Warning: The configuration file '/etc/postfix/main.cf' has been manually modified and will not be updated
postfix:
applied:
pending:
/etc/postfix/main.cf:
status: modified
```
[20:53:52]
<M1k3> De mémoire, les modifications que j'avais apportées consistaient à commenter les lignes :
```
# reject_rbl_client bl.spamcop.net,
# reject_rbl_client cbl.abuseat.org,
# reject_rbl_client zen.spamhaus.org,
```
[20:54:46]
<Aleks (he/him/il/lui)> du coup rajoute --with-diff et propage les modifs a la main
[20:58:36]
<M1k3> > <@Alekswag:matrix.org> du coup rajoute --with-diff et propage les modifs a la main
```
Warning: The configuration file '/etc/postfix/main.cf' has been manually modified and will not be updated
postfix:
applied:
pending:
/etc/postfix/main.cf:
diff: @@ -30,18 +30,11 @@
tls_server_sni_maps = hash:/etc/postfix/sni
-# generated 2020-08-18, Mozilla Guideline v5.6, Postfix 3.4.14, OpenSSL 1.1.1d, intermediate configuration
-# https://ssl-config.mozilla.org/#server=postfix&version=3.4.14&config=intermediate&openssl=1.1.1d&guideline=5.6
+# generated 2023-06-13, Mozilla Guideline v5.7, Postfix 3.7.5, OpenSSL 3.0.9, modern configuration
+# https://ssl-config.mozilla.org/#server=postfix&version=3.7.5&config=modern&openssl=3.0.9&guideline=5.7
-smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
-smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
-smtpd_tls_mandatory_ciphers = medium
-
-# curl https://ssl-config.mozilla.org/ffdhe2048.txt > /path/to/dhparam.pem
-# not actually 1024 bits, this applies to all DHE >= 1024 bits
-smtpd_tls_dh1024_param_file = /usr/share/yunohost/ffdhe2048.pem
-
-tls_medium_cipherlist = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
+smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1, !TLSv1.2
+smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1, !TLSv1.2
tls_preempt_cipherlist = no
@@ -75,11 +68,12 @@
relayhost =
-mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
+mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
+inet_protocols = ipv4
#### Fit to the maximum message size to 25mb, more than allowed by GMail or Yahoo ####
# /!\ This size is the size of the attachment in base64.
@@ -88,7 +82,7 @@
message_size_limit = 35914708
# Virtual Domains Control
-virtual_mailbox_domains = ldap:/etc/postfix/ldap-domains.cf
+virtual_mailbox_domains = /etc/postfix/virtual-mailbox-domains
virtual_mailbox_maps = ldap:/etc/postfix/ldap-accounts.cf,hash:/etc/postfix/app_senders_login_maps
virtual_mailbox_base =
virtual_alias_maps = ldap:/etc/postfix/ldap-aliases.cf,ldap:/etc/postfix/ldap-groups.cf
@@ -128,9 +122,9 @@
smtpd_client_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
-# reject_rbl_client bl.spamcop.net,
-# reject_rbl_client cbl.abuseat.org,
-# reject_rbl_client zen.spamhaus.org,
+ reject_rbl_client bl.spamcop.net,
+ reject_rbl_client cbl.abuseat.org,
+ reject_rbl_client zen.spamhaus.org,
permit
# Requirements for the HELO statement
@@ -171,9 +165,10 @@
smtp_reply_filter = pcre:/etc/postfix/smtp_reply_filter
# Rmilter
-milter_mail_macros = i {mail_addr} {client_addr} {client_name} {auth_authen}
+milter_mail_macros = i {mail_addr} {client_addr} {client_name} {auth_authen} {auth_type}
milter_protocol = 6
-smtpd_milters = inet:localhost:11332
+smtpd_milters = inet:localhost:8891 inet:localhost:11332
+non_smtpd_milters = inet:localhost:8891
# Skip email without checking if milter has died
milter_default_action = accept
@@ -191,3 +186,6 @@
# and after to send spam
disable_vrfy_command = yes
+
+
+
status: modified
```
[21:06:59]
<M1k3> Je ne vois pas ce qui pourrait empêcher aussi bien l'envoi que la réception.
[21:08:15]
<Aleks (he/him/il/lui)> bah là tout de suite je peux pas te faire un cours sur comment postfix et le mail fonctionnent ...
[21:08:26]
<Aleks (he/him/il/lui)> juste propage les modifs qui ne sont pas les tiennes ...
[21:08:55]
<Aleks (he/him/il/lui)> ou bien rajoute --force et refais tes motids
[21:12:51]
<M1k3> > <@Alekswag:matrix.org> ou bien rajoute --force et refais tes motids
Beaucoup plus simple comme ça. 😉
[21:13:58]
<M1k3> Parfait, ça a l'air de refonctionner !!! 🙏🙏🙏🙏🙏
[21:37:47]
<rodinux> it was surely this... it works... also I ask him for add a file `/home/borg/.nobackup` and do a `chmod -R u=rwX,go=--- /home/borg/backup/` as seen in the install script of borgserver_ynh...
[21:40:43]
<Aleks (he/him/il/lui)> still would have been interesting to know the output of `namei -l` before savagely doing the chmod/chown to understand how it happen and prevent it from happening again in the future ...
[21:55:23]
<florent> Aleks (he/him/il/lui): If I remember correctly, the client is borg_ynh, the server is not the yunohost app.
[22:00:44]
<rodinux> yes, is the context... and I haven't access to the server, so I have to ask him... Perhaps I could ask him also to add the key to chroot the user on his server from the client ? can he add it below the `command="......` ?