What type of hardware are you using: Virtual machine
What YunoHost version are you running: YunoHost 12.0.10 (stable).
How are you able to access your server: SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: Title: Error Regenerating SSOWAT Configuration After WordPress Migration – YunoHost 12.0.10
Describe your issue
Hello YunoHost Community,
I am currently experiencing issues with my YunoHost server (Version 12.0.10). During the migration from WordPress, something seems to have gone wrong, and now YunoHost is still attempting to regenerate the configuration for WordPress, even though WordPress is no longer installed. This results in repeated errors and prevents me from successfully performing other configurations.
Problem Description:
After uninstalling WordPress, I receive the following error when running the command yunohost tools regen-conf ssowat --force:
bash
Code kopieren
Info: The operation ‘Regenerate system configurations ‘ssowat’’ could not be completed. Please share the full log of this operation using the command ‘yunohost log share 20250113-200846-regen_conf-ssowat’ to get help
Error: Could not regenerate the configuration for category(s):
When attempting to configure YunoHost, I encounter the error that WordPress is not found in the list of installed apps:
markdown
Code kopieren
Error: Could not find wordpress in the list of installed apps:
- chatgpt-web
- converse
- element
- gancio
- gotosocial
- mastodon
- matterbridge
- pixelfed
- simplex
- snappymail
- synapse
Error: Unknown app
Even after attempting to repair the package configuration with sudo dpkg --configure -a and sudo apt-get install --fix-broken, the problem persists:
markdown
Code kopieren
Error: Could not find wordpress in the list of installed apps:
- chatgpt-web
- converse
- element
- gancio
- gotosocial
- mastodon
- matterbridge
- pixelfed
- simplex
- snappymail
- synapse
dpkg: error processing package yunohost (–configure):
installed yunohost package post-installation script subprocess returned error exit status 1
Steps Already Taken:
Checking for Residual WordPress Files:
No WordPress directories found under /etc/yunohost/apps/.
No remnants found in the database or other configuration files.
Nginx Configuration Warnings:
There are still warnings regarding conflicting server name “” on 0.0.0.0:80, ignored.
Identified and removed faulty Nginx configuration files.
SSOWAT Configuration:
The file /etc/ssowat/conf.json.persistent is correctly formatted.
Permissions of the SSOWAT configuration file checked and corrected.
SSOWAT is not recognized as an installed app, hence it couldn’t be removed or reinstalled.
Log Files:
SSOWAT Regeneration Attempt: https://paste.yunohost.org/raw/renutesobu
Additional Logs: https://paste.yunohost.org/raw/exatifefoc
Additionally, there are repeated OCSP errors in the Nginx logs:
java
Code kopieren
OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org
Questions:
How can I completely remove any remaining references to WordPress so that YunoHost can regenerate the configuration without errors?
What is causing the repeated OCSP errors, and how can I resolve them?
Is there a way to modify the YunoHost post-installation scripts to eliminate the dependency on WordPress?
System Information:
YunoHost Version: 12.0.10
Operating System: Debian 12 (assumed based on package names)
Installed Apps:
chatgpt-web
converse
element
gancio
gotosocial
mastodon
matterbridge
pixelfed
simplex
snappymail
synapse
Summary:
After uninstalling WordPress, YunoHost continues to attempt to regenerate the configuration for WordPress, resulting in errors and blocking system configuration. Additionally, OCSP errors are present in the Nginx logs. I need assistance in removing all remaining references to WordPress and successfully completing the system configuration.
Log Files:
SSOWAT Regeneration Attempt: https://paste.yunohost.org/raw/renutesobu
Additional Logs: https://paste.yunohost.org/raw/exatifefoc
Additionally, there are repeated OCSP errors in the Nginx logs:
java
Code kopieren
OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org
Questions:
How can I completely remove any remaining references to WordPress so that YunoHost can regenerate the configuration without errors?
What is causing the repeated OCSP errors, and how can I resolve them?
Is there a way to modify the YunoHost post-installation scripts to eliminate the dependency on WordPress?
System Information:
YunoHost Version: 12.0.10
Operating System: Debian 12 (assumed based on package names)
Installed Apps:
chatgpt-web
converse
element
gancio
gotosocial
mastodon
matterbridge
pixelfed
simplex
snappymail
synapse
Summary:
After uninstalling WordPress, YunoHost continues to attempt to regenerate the configuration for WordPress, resulting in errors and blocking system configuration. Additionally, OCSP errors are present in the Nginx logs. I need assistance in removing all remaining references to WordPress and successfully completing the system configuration.
Thank you in advance for your help!
Share relevant logs or error messages
https://paste.yunohost.org/raw/exatifefoc args:
dry_run: false
force: true
list_pending: false
names:
- ssowat
with_diff: false
ended_at: 2025-01-13 20:12:23.598114
error: 'Could not regenerate the configuration for category(s): ’
interface: cli
operation: regen_conf
parent: null
related_to: -
- configuration
- ssowat
started_at: 2025-01-13 20:12:23.558531
success: false
yunohost_version: 12.0.10
============
2025-01-13 21:12:23,585: DEBUG - initializing root ldap interface
2025-01-13 21:12:23,597: DEBUG - Formating result in ‘export’ mode
https://darknight-coffee-cannabis.club/
Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.
Thank you for using nginx.
root@srv /home/carrabelloy # sudo systemctl status yunohost-api
sudo systemctl status postfix
sudo systemctl status dovecot
sudo systemctl status nginx
● yunohost-api.service - YunoHost API Server
Loaded: loaded (/etc/systemd/system/yunohost-api.service; enabled; preset:>
Active: active (running) since Mon 2025-01-13 21:03:29 CET; 15h ago
Main PID: 2393567 (python3)
Tasks: 1 (limit: 76833)
Memory: 80.4M
CPU: 25.399s
CGroup: /system.slice/yunohost-api.service
└─2393567 python3 /usr/bin/yunohost-api
Jan 13 21:03:29 srv.darknight-coffee.org systemd[1]: Started yunohost-api.servi>
lines 1-11/11 (END)
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/lib/systemd/system/postfix.service; enabled; preset: enab>
Active: active (exited) since Thu 2025-01-09 09:02:14 CET; 5 days ago
Docs: man:postfix(1)
Process: 2394441 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 1222755 (code=exited, status=0/SUCCESS)
CPU: 2ms
Jan 12 12:38:47 srv.darknight-coffee.org systemd[1]: Reloading postfix.service >
Jan 12 12:38:47 srv.darknight-coffee.org systemd[1]: Reloaded postfix.service →
Jan 13 21:03:16 srv.darknight-coffee.org systemd[1]: Reloading postfix.service >
Jan 13 21:03:16 srv.darknight-coffee.org systemd[1]: Reloaded postfix.service →
Jan 13 21:03:16 srv.darknight-coffee.org systemd[1]: Reloading postfix.service >
Jan 13 21:03:16 srv.darknight-coffee.org systemd[1]: Reloaded postfix.service →
Jan 13 21:05:52 srv.darknight-coffee.org systemd[1]: Reloading postfix.service >
Jan 13 21:05:52 srv.darknight-coffee.org systemd[1]: Reloaded postfix.service →
Jan 13 21:05:54 srv.darknight-coffee.org systemd[1]: Reloading postfix.service >
Jan 13 21:05:54 srv.darknight-coffee.org systemd[1]: Reloaded postfix.service →
lines 1-18/18 (END)
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/lib/systemd/system/dovecot.service; enabled; preset: enab>
Active: active (running) since Mon 2025-01-13 21:06:35 CET; 15h ago
Docs: man:dovecot(1)
https://doc.dovecot.org/
Main PID: 2395440 (dovecot)
Status: “v2.3.19.1 (9b53102964) running”
Tasks: 5 (limit: 76833)
Memory: 4.3M
CPU: 676ms
CGroup: /system.slice/dovecot.service
├─2395440 /usr/sbin/dovecot -F
├─2395451 dovecot/anvil
├─2395452 dovecot/log
├─2395458 dovecot/config
└─2424782 dovecot/stats
Jan 14 07:01:13 srv.darknight-coffee.org dovecot[2395452]: imap-login: Disconne>
Jan 14 07:21:02 srv.darknight-coffee.org dovecot[2395452]: imap-login: Disconne>
Jan 14 07:21:02 srv.darknight-coffee.org dovecot[2395452]: imap-login: Disconne>
Jan 14 07:58:24 srv.darknight-coffee.org dovecot[2395452]: imap-login: Disconne>
Jan 14 09:20:07 srv.darknight-coffee.org dovecot[2395440]: master: Warning: Tim>
Jan 14 11:49:13 srv.darknight-coffee.org dovecot[2395452]: imap-login: Disconne>
lines 1-23
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enable>
Active: active (running) since Mon 2025-01-13 21:14:49 CET; 15h ago
Docs: man:nginx(8)
Process: 2397891 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_pr>
Process: 2397892 ExecStart=/usr/sbin/nginx -g daemon on; master_process on;>
Main PID: 2397899 (nginx)
Tasks: 9 (limit: 76833)
Memory: 164.1M
CPU: 2min 28.593s
CGroup: /system.slice/nginx.service
├─2397899 "nginx: master process /usr/sbin/nginx -g daemon on; mas>
├─2397900 “nginx: worker process”
├─2397901 “nginx: worker process”
├─2397902 “nginx: worker process”
├─2397903 “nginx: worker process”
├─2397904 “nginx: worker process”
├─2397905 “nginx: worker process”
├─2397906 “nginx: worker process”
└─2397907 “nginx: worker process”
Jan 13 21:14:49 srv.darknight-coffee.org systemd[1]: Starting nginx.service - A>
Jan 13 21:14:49 srv.darknight-coffee.org nginx[2397891]: 2025/01/13 21:14:49 [i>
lines 1-23
root@srv /home/carrabelloy # sudo yunohost log share 20250113-201223-regen_conf-ssowat
Info: This log is now available via https://paste.yunohost.org/raw/exatifefoc
root@srv /home/carrabelloy # sudo tail -n 50 /var/log/nginx/error.log
sudo tail -n 50 /var/log/nginx/srv.darknight-coffee.org-error.log
sudo tail -n 50 /var/log/nginx/carrabelloy.darknight-coffee.org-error.log
2025/01/14 12:14:32 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:16:59 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:17:15 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:17:59 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.168.117:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:18:00 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:18:01 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 23.32.238.27:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:18:45 [error] 2397900#2397900: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:19:33 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 23.32.238.27:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:20:06 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:20:18 [error] 2397905#2397905: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.202.121:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:21:04 [error] 2397905#2397905: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 23.32.238.27:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:21:59 [error] 2397906#2397906: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.106:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:22:17 [error] 2397906#2397906: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.168.117:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:24:16 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.114:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:24:38 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:25:57 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.202.121:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:26:10 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.202.121:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:26:18 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 23.32.238.27:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:26:18 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:26:57 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:27:50 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:28:10 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 23.32.238.27:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:29:23 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:29:37 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 184.25.51.16:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:30:53 [error] 2397904#2397904: r10.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: r10.o.lencr.org, certificate: “/etc/yunohost/certs/darknight-coffee-cannabis.club/crt.pem”
2025/01/14 12:31:13 [error] 2397900#2397900: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:31:13 [error] 2397900#2397900: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:31:20 [error] 2397900#2397900: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 2.16.168.113:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:32:15 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.168.117:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:32:15 [error] 2397905#2397905: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 184.25.51.82:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:32:20 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:32:40 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:32:40 [error] 2397905#2397905: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 184.25.51.82:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:32:41 [error] 2397907#2397907: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:33:15 [error] 2397905#2397905: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 2.16.202.121:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:33:47 [error] 2397906#2397906: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:34:15 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 184.25.51.75:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:34:20 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.15:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:35:17 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.202.121:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:36:04 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:36:45 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 184.25.51.75:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:36:53 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 184.25.51.82:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:37:05 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 2.16.168.113:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.org/crt.pem”
2025/01/14 12:37:11 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/netz.darknight-coffee.eu/crt.pem”
2025/01/14 12:37:20 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.com/crt.pem”
2025/01/14 12:38:07 [error] 2397904#2397904: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 2.16.241.8:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:38:07 [error] 2397903#2397903: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:38:07 [error] 2397900#2397900: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r10.o.lencr.org, peer: 23.55.163.58:80, certificate: “/etc/yunohost/certs/darknight-coffee.org/crt.pem”
2025/01/14 12:39:25 [error] 2397901#2397901: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
2025/01/14 12:40:02 [error] 2397902#2397902: OCSP response not successful (6: unauthorized) while requesting certificate status, responder: r11.o.lencr.org, peer: 95.101.54.131:80, certificate: “/etc/yunohost/certs/darknight-coffee.eu/crt.pem”
root@srv /home/carrabelloy # sudo dpkg --configure -a
Setting up systemd-sysv (252.33-1~deb12u1) …
Setting up yunohost (12.0.10) …
Regenerating configuration, this might take a while…
Error: Could not find wordpress in the list of installed apps:
- chatgpt-web
- converse
- element
- gancio
- gotosocial
- mastodon
- matterbridge
- pixelfed
- simplex
- snappymail
- synapse
dpkg: error processing package yunohost (–configure):
installed yunohost package post-installation script subprocess returned error exit status 1
Setting up libnss-systemd:amd64 (252.33-1~deb12u1) …
Setting up libfdisk1:amd64 (2.38.1-5+deb12u3) …
Setting up mount (2.38.1-5+deb12u3) …
Setting up libpam-systemd:amd64 (252.33-1~deb12u1) …
Processing triggers for libc-bin (2.36-9+deb12u9) …
Errors were encountered while processing:
yunohost
root@srv /home/carrabelloy # sudo apt-get install --fix-broken
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up yunohost (12.0.10) …
Regenerating configuration, this might take a while…
Error: Could not find wordpress in the list of installed apps: - chatgpt-web
- converse
- element
- gancio
- gotosocial
- mastodon
- matterbridge
- pixelfed
- simplex
- snappymail
- synapse
dpkg: error processing package yunohost (–configure):
installed yunohost package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
yunohost
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@srv /home/carrabelloy #