Same kind of issue after fresh install of debian on arm64 board related to mising signature running apt update
full log of nextcloud install
For me running yunohost tools regen-conf apt --force solve the issue.
[FAILED] Failed to listen on sssd-nss.socke… SSSD NSS Service responder socket.
See 'systemctl status sssd-nss.socket' for details.
[FAILED] Failed to listen on sssd-pam.socke… SSSD PAM Service responder socket.
See 'systemctl status sssd-pam.socket' for details.
[FAILED] Failed to listen on sssd-ssh.socke… SSSD SSH Service responder socket.
See 'systemctl status sssd-ssh.socket' for details.
[FAILED] Failed to listen on sssd-sudo.sock…SSSD Sudo Service responder socket.
See 'systemctl status sssd-sudo.socket' for details.
Open issue: Trixie: Failed to listen on sssd-*.socket · Issue #2705 · YunoHost/issues · GitHub
Hi 
Got this error when going in “Hard drives” in the web admin interface : hastebin
Hi, I tried to start the migration, but it fails very quickly: https://paste.yunohost.org/raw/forupowonu
From what I saw, pipx is used by Immich, and to freeze, we should run /opt/pipx/venvs/uv/bin/uv pip freeze
I have reported this kind of related error due to the locales package not correctly installed / corrupted on GitHub:
AFAIK, this issue exists in Trixie AND Bookworm.
This is a critical issue for the RosarioSIS app. It can’t pass tests if the locale (French, fr_FR.UTF-8 for example) can’t be correctly installed due to errors / files missing.
1 Like
Hello there, first post 
Success stry below :
I just installed a fresh trixie on raspberry pi 5.
Then quickly installed yunohost as I had done for a previous install, except of course I used the testing branch.
However there were a few quirks
I missed the point when the install allows to restore a previous backup, as after the first install I was forced to do yunohost postinstall, where I had no choice to declare a new domain (used a local one) and the install finished but without correct settings. Only after that was I able to use yunohost commands from the shell, manually copy backup files, and restore them (that worked, had to restart to get the hostname updated)
After that everthing seems to work :
- apps: redirect, phpsysinfo, mattermost all restored ok. Later installed forgejo and it works well too
- users were recreated, and so far so good
- network and DNS are ok (using *****.ynh.fr)
That’s all
1 Like
I’m still having the same issue reported daily, it seems to be a setting that was not properly migrated from nssswitch to libnss.
Any clue on how to override this warning?
Hello, I got an issue trying to install above DietPi based on Debian 13
[1m 5/5 • Installing YunoHoste[0m
===================
Running: apt-get install --assume-yes -o Dpkg::Options::=--force-confold -o APT::install-recommends=true yunohost yunohost-admin postfix
===================
Reading package lists...
Building dependency tree...
Reading state information...
Solving dependencies...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
yunohost : Depends: postsrsd but it is not installable
Recommends: yunohost-portal (>= 12.1) but it is not going to be installed
Recommends: ntp but it is not installable
Recommends: rsyslog but it is not going to be installed
Recommends: unattended-upgrades but it is not going to be installed
Recommends: libdbd-ldap-perl but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. yunohost:armhf=13.0.1 is selected for install
2. yunohost:armhf Depends postsrsd
but none of the choices are installable:
[no choices]
[e[1me[31mFAILe[0m] Installation of YunoHost packages failed
[e[1me[34mINFOe[0m] Installation logs are available in /var/log/yunohost-installation_20251204_220425.log
Here’s the output of sudo apt policy postsrsd
postsrsd:
Installed: (none)
Candidate: (none)
Version table:
Urhg wokay, it’s weird that postsrsd has no candidate at all ..
Can you try to apt update and then apt policy postsrsd again ? Or something like apt install postsrsd ntp rsyslog ?
No change, here’s the output of apt install postsrsd ntp rsyslog
Package ntp is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
openntpd ntpsec
Package postsrsd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Error: Package 'postsrsd' has no installation candidate
Error: Package 'ntp' has no installation candidate
Here’s the sources of my system. I didn’t mentionned it earlier, an Odroid HC2 is ARM based.
Hit:1 http://repo.yunohost.org/debian trixie InRelease
Hit:2 https://deb.debian.org/debian trixie InRelease
Hit:3 https://deb.debian.org/debian trixie-updates InRelease
Hit:4 https://deb.debian.org/debian-security trixie-security InRelease
Hit:5 https://deb.debian.org/debian trixie-backports InRelease
Hit:6 https://dietpi.com/apt trixie InRelease
Hit:7 https://dietpi.com/apt all InRelease
Hmokay, ntp really seem to not exists anymore, which we should probably dig into (it’s only a “Recommends” though so not 100% necessary)
However postsrsd definitely exists : Debian -- Details of package postsrsd in trixie
so I don’t get why the system doesn’t find any install candidat for it …
You sure that apt update is happy ?
Everything looks fine on my installation. However, when I go to the “Hard drives” section, a table with this error pops up. I can probably live with it for now, but I’ll let you know about it here just in case. 
Error: “500”
Action: “GET” /yunohost/api/storage/disk/list?with_info&human_readable_size
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/moulinette/interfaces/api.py”, line 430, in process
ret = self.actionsmap.process(arguments, timeout=30, route=_route)
File “/usr/lib/python3/dist-packages/moulinette/actionsmap.py”, line 580, in process
return func(**arguments)
File “/usr/lib/python3/dist-packages/yunohost/storage.py”, line 22, in storage_disk_list
return disk_list(**kargs)
File “/usr/lib/python3/dist-packages/yunohost/disk.py”, line 90, in disk_list
disks = Udisks2Manager(bus).get_disks()
File “/usr/lib/python3/dist-packages/yunohost/utils/udisks2_interfaces.py”, line 78, in get_disks
for object_path, (iface, props) in parse_get_managed_objects(
~~~~~~~~~~~~~~~~~~~~~~~~~^
(Disk, AtaDisk, NvmeDisk),
^^^^^^^^^^^^^^^^^^^^^^^^^^
…<2 lines>…
on_unknown_member=“ignore”,
^^^^^^^^^^^^^^^^^^^^^^^^^^^
).items():
^
File “/usr/lib/python3/dist-packages/yunohost/utils/udisks2_interfaces.py”, line 63, in parse_get_managed_objects
return sdbus_parse_get_managed_objects(
interfaces, managed_objects_data, on_unknown_interface, on_unknown_member
)
File “/usr/lib/python3/dist-packages/sdbus/utils/parse.py”, line 383, in parse_get_managed_objects
_get_class_from_interfaces(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
interfaces_to_class_map,
^^^^^^^^^^^^^^^^^^^^^^^^
…<2 lines>…
use_interface_subsets,
^^^^^^^^^^^^^^^^^^^^^^
)
^
File “/usr/lib/python3.13/unittest/mock.py”, line 1169, in call
return self._mock_call(*args, **kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.13/unittest/mock.py”, line 1173, in _mock_call
return self._execute_mock_call(*args, **kwargs)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.13/unittest/mock.py”, line 1234, in _execute_mock_call
result = effect(*args, **kwargs)
TypeError: _get_class_from_interfaces() takes 3 positional arguments but 4 were given
Plus, I’m adding the last thing that I’ve been monitoring since yesterday, when I installed Yuno on a fresh VPS. The thing is, the “yunohost-api” service likes to crash a lot (Error: “502” / Action: “PUT” /yunohost/api/diagnosis/run?expect_if_never_ran_yet) and has to be restarted. I’m attaching the log here: hastebin
Whats the current state of trixie on yunohost?
will this come officialy or will be manually upgraded?
It usually arrives as a migration but can be done via interface
hi,
Piwigo fails to install, even if fixing the APT issue decribed in 🎃 YunoHost 13.0 / Trixie spooky beta - #31 by daneel
There’s a warning then an error near the end of the installation log:
> 2025-12-14 15:45:29,465: DEBUG - + status=‘SUCCESS Permission ‘‘‘piwigo.main’’’ updated
> 2025-12-14 15:45:29,479: WARNING - jq: parse error: Invalid numeric literal at line 1, column 8
> 2025-12-14 15:45:29,490: DEBUG - {“stat”:“ok”,“result”:{“username”:“yunolxc”,“status”:“webmaster”,“theme”:“modus”,“language”:“fr_FR”,“pwg_token”:“e613f418111d8318b5f648191cc3bd3a”,“charset”:“utf-8”,“current_datetime”:“2025-12-14 15:45:28”,“version”:“16.1.0”,“save_visits”:false,“connected_with”:“ws_session_login”,“available_sizes”:\[“square”,“thumb”,“2small”,“xsmall”,“small”,“medium”,“large”,“xlarge”,“xxlarge”\],“upload_file_types”:“jpg,jpeg,png,gif,webp”,“upload_form_chunk_size”:500}}SUCCESS Permission ‘‘‘piwigo.main’’’ updated’
> 2025-12-14 15:45:29,492: DEBUG - ++ jq --raw-output .result.pwg_token
> 2025-12-14 15:45:29,492: DEBUG - ++ jq --raw-output .result.pwg_token
> 2025-12-14 15:45:29,492: DEBUG - + pwg_token=
> 2025-12-14 15:45:29,493: DEBUG - + ynh_exit_properly
> 2025-12-14 15:45:29,493: DEBUG - + local exit_code=5
> 2025-12-14 15:45:29,493: DEBUG - + \[\[ install =\~ ^install$|^upgrade$|^restore$ \]\]
> 2025-12-14 15:45:29,494: DEBUG - + rm -rf /var/cache/yunohost/download/
> 2025-12-14 15:45:29,494: DEBUG - + ‘\[’ 5 -eq 0 ‘\]’
> 2025-12-14 15:45:29,495: DEBUG - + trap ‘’ EXIT
> 2025-12-14 15:45:29,495: DEBUG - + set +o errexit
> 2025-12-14 15:45:29,495: DEBUG - + set +o nounset
> 2025-12-14 15:45:29,496: DEBUG - + sleep 0.5
> 2025-12-14 15:45:29,981: DEBUG - + exit 1
> 2025-12-14 15:45:30,089: ERROR - Impossible d’installer piwigo : Une erreur est survenue dans le script d’installation de l’applicationI tried updating to Trixie, seems like the Debian update went fine, but the yunohost one didn’t. Now I am stuck at Trixie but yunohost doesn’t run. Any ideas on how to fix this?
If you already ran the Bookworm → Trixie migration, then this error is symptomatic of the fact that the migration procedure was not 100% succesful (otherwise YunoHost would have flagged it as completed). It is recommended to investigate what happened with the support team, who will need the full log of the migration, which can be found in Tools > Logs in the webadmin.
Ideally it’s cool if you can find and share the log of the partially-failed migration. If the webadmin is not accessible, you can try from the command line with yunohost log list | grep migrat, find the ID corresponding to your very first migration attempt, and share the corresponding log with yunohost log share <id>
First try with cloudflared issue: https://paste.yunohost.org/raw/hobanecuye
Second try with cloudflared issue solved: https://paste.yunohost.org/raw/ucoqapifak