Bonjour Ă tous,
Merci pour cette mise Ă jour qui sâest globalement bien passĂ©e pour moi hormis ceci :
https://paste.yunohost.org/raw/okosofusec
Bonjour,
Jâai eu le mĂȘme souci. Câest sans doute liĂ© Ă des installations âanciennesâ de YunoHost du temps oĂč la gestion des alias nâĂ©tait pas la mĂȘme quâaujourdâhui.
Jâai rĂ©solu en supprimant les aliases de lâadministrateur du domaine via la webadmin.
root@ton_domaine.tld et admin@ton_domaine.tld.
La migration 0034 a pu se faire et ça a lancé automatiquement la migration 35.
ppr
3 Likes
Bonjour ppr,
Merci pour ta rĂ©ponse, câĂ©tait effectivement la solution 
Bonne journée 
1 Like
De mon cotĂ© depuis la MĂ J, je ne semble plus ĂȘtre en capacitĂ© de recevoir les mails.
Les envois ont lâair de bien se passer (ça arrive dans les Ă©lĂ©ments envoyĂ©s) mais rien en rĂ©ception (mĂȘme depuis lâinstance Roundcube sur mon serveur).
@Yop : Est-ce que yunohost tools regen-conf postfix --dry-run --with-diff raconte des choses
VoilĂ ce que jâai comme rĂ©sultat :
Warning: The configuration file '/etc/postfix/sasl_passwd' has been manually modified and will not updated
postfix:
applied:
pending:
/etc/postfix/sasl_passwd:
diff: @@ -1 +0,0 @@-[mail.hebergeur.com]:465 monserveur@mondomaine.tld:<une suite de chiffres et lettres)
status: modified
Et jâignore si câest liĂ© (jâai pas eu vraiment le temps dâenquĂȘter dessus) mais jâai Ă©galement un problĂšme avec mon VPN. Je pourrais essayer de le dĂ©sinstaller/rĂ©installer pour voir (le problĂšme du mail est plus important pour moi).
Same problem here⊠Iâm in version 12.1.15.1 and I cannot edit aliases without using the admin interface, although the option is activated.
1 Like
Hello there,
updated this morning and slapd service couldnât migrate. I was waiting for the error to finish in order to get the logs and retry the migrations later or relaunch slapd service,
But I got ejected after 10minutes, I cannot log in my server anymore (ssh/webui all refusing, including the local old first-user access (not a ynh user at all). My personal ssh-user is logged-in with ssh-key but I guess some services donât run or canât read it 
.
Will reboot the server in rescue-live (from my hosting provider) and see if I can manage to repair (at least allow my ssh connection without ssh-key for the work-restore process)
Will post updates if I find a way to reaccess.
Edit: was able to login to rescue-live iso from my hosting provider; got to chroot, and slapd canât start at all. I have done some cleaning in the ssh config (separate ssh from ldap as the service fails), and reboot. Now I can login through webui (???), but not ssh.
slapd fails with :
Aug 25 11:13:30 systemd[1]: slapd.service: Scheduled restart job, restart counter is at 159.
Aug 25 11:13:30 systemd[1]: Stopped slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Aug 25 11:13:30 systemd[1]: Starting slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Aug 25 11:13:30 slapd[5640]: @(#) $OpenLDAP: slapd 2.5.13+dfsg-5 (Feb 8 2023 01:56:12) $
Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Aug 25 11:13:30 slapd[5641]: slapd starting
Aug 25 11:13:30 slapd[5641]: daemon: listen(ldap://localhost:389/, 5) failed errno=98 (Address already in use)
Aug 25 11:13:30 slapd[5641]: listener initialization failed
Aug 25 11:13:30 slapd[5635]: Starting OpenLDAP: slapd.
Aug 25 11:13:30 systemd[1]: Started slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Aug 25 11:13:30 slapd[5641]: slapd stopped.
Aug 25 11:13:30 slapd[5643]: Stopping OpenLDAP: slapd.
Aug 25 11:13:30 systemd[1]: slapd.service: Deactivated successfully.
Aug 25 11:13:33 systemd[1]: slapd.service: Scheduled restart job, restart counter is at 160.
Aug 25 11:13:33 systemd[1]: Stopped slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Aug 25 11:13:33 systemd[1]: Starting slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Aug 25 11:13:33 slapd[5665]: @(#) $OpenLDAP: slapd 2.5.13+dfsg-5 (Feb 8 2023 01:56:12) $
Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Aug 25 11:13:33 slapd[5666]: slapd starting
Aug 25 11:13:33 slapd[5666]: daemon: listen(ldap://localhost:389/, 5) failed errno=98 (Address already in use)
Aug 25 11:13:33 slapd[5666]: listener initialization failed
Aug 25 11:13:33 slapd[5660]: Starting OpenLDAP: slapd.
Aug 25 11:13:33 systemd[1]: Started slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Aug 25 11:13:33 slapd[5666]: slapd stopped.
Aug 25 11:13:33 slapd[5668]: Stopping OpenLDAP: slapd.
Aug 25 11:13:33 systemd[1]: slapd.service: Deactivated successfully.
I will probably migrate my system to a new server (I have daily ynh backups at home), but I will try to continue checking if it is possible to repair it.
Bonjour,
Jâai apparemment le mĂȘme souci 0034 jâai ouvert une discussion dans support :Migration 0034_fix_missing_admins_aliases a Ă©chouĂ©
Car je ne comprends pas comment supprimer les aliases de lâadministrateur du domaine via la webadmin ?
Cauchy
Peut-ĂȘtre la solution ici 
Not totally surprised that slapd canât start in a chroot (though not 100% sure thatâs the issue)
In the log you shared we can see:
daemon: listen(ldap://localhost:389/, 5) failed errno=98 (Address already in use)
which suggests something else listens to port 389
Itâs also unclear why the upgrade would have broken the service ⊠whatâs migrated is not the slapd service itself (whatever that would mean) but the data itâs holding ⊠if the data migration failed then the first step should be to share the log of the failed migration
1 Like
Hello Aleks
I would have loved to but the yunohost command has crashed, kicking me of the ssh and I havenât been able to login back since, so I wasnât ever able to share (nor view) the yunohost log.
I donât know what failed in the migrations, I was going for a yunohost tools upgrade --system and I just happened to see some errors about slapd not being able to restart and then I never got hand on my system again.
In chroot, I have never been able to use much yunohost command either, with the slapd service being off and unable to restart, which is probably normal in chroot, but wasnât during the process of migrating. I am pretty sure I never toyed with the slapd conf.
I am currently reconfiguring a server to migrate my backup on it in order to not lock out my family for too long.
But I will keep on trying to get those yunohost logs on the down server before I erase it.
Thanks a lot for your answers.
Edit: almost finished restoring my server elsewhere, before deleting the old one (end of month) I have been able (by jumping through quite a few hoops on the chroot) to relog into my server on the ynh system (not rescue+chroot) with ROOT only.
I have been able to pull out some yunohost commands.
The first log from yesterday (all happened yesterday) fails already because of slapd not running, weirdly it seemed it was off first.
https://paste.yunohost.org/raw/awivunisur
then most the tasks fails as seen here :
yunohost log list
35:
description: Create a backup archive
name: 20250824-133002-backup_create
path: /var/log/yunohost/operations/20250824-133002-backup_create.yml
started_at: 2025-08-24 15:30:02
success: True
36:
description: Upgrade system packages
name: 20250825-063917-tools_upgrade
path: /var/log/yunohost/operations/20250825-063917-tools_upgrade.yml
started_at: 2025-08-25 08:39:17
success: ?
37:
description: Restore system from a backup archive
name: 20250825-081811-backup_restore_system
path: /var/log/yunohost/operations/20250825-081811-backup_restore_system.yml
started_at: 2025-08-25 10:18:11
success: False
38:
description: Regenerate system configurations 'all'
name: 20250825-081926-regen_conf-all
path: /var/log/yunohost/operations/20250825-081926-regen_conf-all.yml
started_at: 2025-08-25 10:19:26
success: ?
39:
description: Run migrations
name: 20250825-090442-tools_migrations_migrate_forward
path: /var/log/yunohost/operations/20250825-090442-tools_migrations_migrate_forward.yml
started_at: 2025-08-25 11:04:42
success: False
40:
description: Run migrations
name: 20250825-090509-tools_migrations_migrate_forward
path: /var/log/yunohost/operations/20250825-090509-tools_migrations_migrate_forward.yml
started_at: 2025-08-25 11:05:09
success: False
41:
description: Create a backup archive
name: 20250825-092009-backup_create
path: /var/log/yunohost/operations/20250825-092009-backup_create.yml
started_at: 2025-08-25 11:20:09
success: True
42:
description: Upgrade the 'jellyseerr' app
name: 20250825-093612-app_upgrade-jellyseerr
path: /var/log/yunohost/operations/20250825-093612-app_upgrade-jellyseerr.yml
started_at: 2025-08-25 11:36:12
success: False
43:
description: Restore system from a backup archive
name: 20250825-170026-backup_restore_system
path: /var/log/yunohost/operations/20250825-170026-backup_restore_system.yml
started_at: 2025-08-25 19:00:26
success: False
44:
description: Regenerate system configurations 'all'
name: 20250825-170139-regen_conf-all
path: /var/log/yunohost/operations/20250825-170139-regen_conf-all.yml
started_at: 2025-08-25 19:01:39
success: False
45:
description: Create a backup archive
name: 20250825-204956-backup_create
path: /var/log/yunohost/operations/20250825-204956-backup_create.yml
started_at: 2025-08-25 22:49:56
success: False
apparently all happened because slapd wasnât running, why is that so (my family and I use the yunohost server daily, all day long) I canât seem to understand, but everything fails from this point forward.
If Iâm spamming a topic that isnât the right one, please feel free to move my post/s if needed, if some logs from the list above needs to be shared please ask.
For now I can see that my former server has no permissions set, at all. This explains why i cannot connect with my user anymore, but not why those were erased 
.
As for my part, I think Yunohost is an awesome project, I will probably manage to make all my services back online soon without any help, but I might try to understand what happened anyways.
Si, dans comptes â premier utilisateur
voir ma discussion ici : Migration 0034_fix_missing_admins_aliases a échoué - #4 by ppr
câest rĂ©solu pour moi !
1 Like
Can you please enable the bypass update for selected one app. i only want to update one update and not all-
I am getting a bunch of files written to /
john@yunohost:~$ ls -a /
. .20250824-040607-settings_set.logstreamcache
.. .20250824-043036-settings_set.logstreamcache
.20250820-135109-tools_migrations_migrate_forward.logstreamcache .20250824-043111-settings_set.logstreamcache
.20250820-135113-regen_conf-all.logstreamcache .20250824-043824-user_update-john.logstreamcache
.20250820-135427-tools_migrations_migrate_forward.logstreamcache .20250824-052858-tools_update.logstreamcache
.20250820-135609-tools_migrations_migrate_forward.logstreamcache .20250824-052917-tools_upgrade.logstreamcache
.20250820-135610-tools_migrations_migrate_forward.logstreamcache .20250824-054826-tools_reboot.logstreamcache
.20250820-135611-diagnosis_run.logstreamcache .20250824-055018-tools_reboot.logstreamcache
.20250820-135833-tools_update.logstreamcache .20250824-141355-diagnosis_run.logstreamcache
.20250820-141732-tools_update.logstreamcache .20250824-141506-tools_update.logstreamcache
.20250820-141739-diagnosis_run.logstreamcache .20250825-021119-diagnosis_run.logstreamcache
.20250821-021537-diagnosis_run.logstreamcache .20250825-134728-tools_update.logstreamcache
.20250821-133100-tools_update.logstreamcache .20250825-140328-diagnosis_run.logstreamcache
.20250821-134016-regen_conf-all.logstreamcache .20250826-021240-diagnosis_run.logstreamcache
.20250821-134126-tools_migrations_migrate_forward.logstreamcache app.db
.20250821-134128-diagnosis_run.logstreamcache bin
.20250821-134239-tools_update.logstreamcache boot
.20250821-141702-diagnosis_run.logstreamcache dev
.20250821-183923-app_remove-xxxx.logstreamcache etc
.20250821-184655-app_remove-xxxx.logstreamcache home
.20250821-185110-app_remove-xxxx.logstreamcache lib
.20250821-185133-app_remove-xxxx.logstreamcache lib64
.20250822-021800-diagnosis_run.logstreamcache lost+found
.20250822-133347-tools_update.logstreamcache media
.20250822-141146-diagnosis_run.logstreamcache mnt
.20250822-161937-app_config_set-redirect__5.logstreamcache opt
.20250822-162431-app_config_set-redirect__4.logstreamcache proc
.20250822-162622-app_config_set-redirect.logstreamcache root
.20250822-162724-app_config_set-redirect__5.logstreamcache run
.20250823-021617-diagnosis_run.logstreamcache sbin
.20250823-134303-tools_update.logstreamcache srv
.20250823-134338-tools_upgrade.logstreamcache sys
.20250823-140316-tools_update.logstreamcache tmp
.20250823-141358-diagnosis_run.logstreamcache usr
.20250824-021303-diagnosis_run.logstreamcache var
.20250824-040507-settings_set.logstreamcache
same
Je me retrouve avec un problĂšme que je nâavais pas ce matin.
Il y a plus dâun an, jâavais activĂ© la restriction dâaccĂšs Webadmin, avec cet exemple dâ @OniriCorpe : Webadmin : La restriction d'accĂšs ne fonctionne pas - #4 by OniriCorpe
et ça a fonctionnĂ© sans problĂšme jusquâĂ maintenant.
Je me retrouve avec 403 Forbidden
Jâai suivi les infos de @rodinux plus bas, sur la mĂȘme page, pour rĂ©soudre le problĂšme.
Voici la rĂ©ponse qui jâai : La clĂ© de filtre '('security', 'webadmin', 'allowlist')' est incorrecte.
Je ne sais plus quoi faire.
Je précise que je peux accéder à mes applis, ssh, mais plus Webadmin
les commandes ont changer pour les settings avec Yunohost 12
Pour activer ou desactiver les filtres
yunohost settings set security.webadmin.webadmin_allowlist_enabled -v 0 #( 0 = no, 1 = yes)
Par contre pour ajouter une IP en ligne de commande jâai une erreur
yunohost settings set security.webadmin.webadmin_allowlist -v xx.xxx.xx.xxx
========================================
>>>> Security
========================================
# Webadmin
Traceback (most recent call last):
File "/usr/bin/yunohost", line 108, in <module>
main()
File "/usr/bin/yunohost", line 97, in main
yunohost.cli(
File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 59, in cli
ret = moulinette.cli(
^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 143, in cli
).run(args, output_as=output_as, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 530, in run
ret = self.actionsmap.process(args, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 580, in process
return func(**arguments)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 532, in func_wrapper
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/settings.py", line 105, in settings_set
return settings.set(key, value, args, args_file, operation_logger=operation_logger)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/configpanel.py", line 596, in set
self.form = self._ask(
^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/configpanel.py", line 897, in _ask
form = prompt_or_validate_form(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/form.py", line 2134, in prompt_or_validate_form
if not option.is_visible(context):
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/form.py", line 435, in is_visible
return evaluate_simple_js_expression(self.visible, context=context) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/form.py", line 224, in evaluate_simple_js_expression
return evaluate_simple_ast(node, context) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/utils/form.py", line 109, in evaluate_simple_ast
return context[node.id]
~~~~~~~^^^^^^^^^
KeyError: 'webadmin_allowlist_enabled'
3 Likes
Mais par contre, en activant lâaccĂšs Ă la webadmin yunohost settings set security.webadmin.webadmin_allowlist_enabled -v 0 je peux configurer une IP et activer et ça fonctionne en sauvegardant la confâŠ
3 Likes