Hello everyone,
Rien ne va plus depuis ma tentative de passage à Bullseye.
Sur une Lime1, j’ai :
# yunohost --version
yunohost:
repo: stable
version: 4.4.2.1
yunohost-admin:
repo: stable
version: 4.4.1
moulinette:
repo: stable
version: 4.4.1
ssowat:
repo: stable
version: 4.4.1
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Mais …
`# yunohost diagnosis show --issue
reports:
0:
description: Internet connectivity
id: ip
items:
details: Having a working IPv6 is not mandatory for your server to work, but it is better for the health of the Internet as a whole. IPv6 should usually be automatically configured by the system or your provider if it's available. Otherwise, you might need to configure a few things manually as explained in the documentation here: https://yunohost.org/#/ipv6. If you cannot enable IPv6 or if it seems too technical for you, you can also safely ignore this warning.
status: WARNING
summary: The server does not have working IPv6.
1:
description: Ports exposure
id: ports
items:
0:
details:
- Exposing this port is needed for email features (service postfix)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 25 is not reachable from outside.
1:
details:
- Exposing this port is needed for email features (service postfix)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 587 is not reachable from outside.
2:
details:
- Exposing this port is needed for email features (service dovecot)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 993 is not reachable from outside.
3:
details:
- Exposing this port is needed for [?] features (service ssh)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 1532 is not reachable from outside.
4:
details:
- Exposing this port is needed for xmpp features (service metronome)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 5222 is not reachable from outside.
5:
details:
- Exposing this port is needed for xmpp features (service metronome)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 5269 is not reachable from outside.
6:
details:
- Exposing this port is needed for [?] features (service syncthing)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 22000 is not reachable from outside.
2:
description: Email
id: mail
items:
0:
details:
- You should first try to unblock outgoing port 25 in your internet router interface or your hosting provider interface. (Some hosting provider may require you to send them a support ticket for this).
- Some providers won't let you unblock outgoing port 25 because they don't care about Net Neutrality.
- Some of them provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://yunohost.org/#/vpn_advantage
- You can also consider switching to a more net neutrality-friendly provider
status: ERROR
summary: The SMTP mail server cannot send emails to other servers because outgoing port 25 is blocked in IPv4.
1:
details: Could not open a connection on port 25 to your server in IPv4. It appears to be unreachable.
1. The most common cause for this issue is that port 25 is not correctly forwarded to your server.
2. You should also make sure that service postfix is running.
3. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
status: ERROR
summary: The SMTP mail server is unreachable from the outside on IPv4. It won't be able to receive emails.
2:
details:
- Current reverse DNS: 77.109.97.197.adsl.dyn.edpnet.net
Expected value: harpo-bzh.nohost.me
- You should first try to configure the reverse DNS with harpo-bzh.nohost.me in your internet router interface or your hosting provider interface. (Some hosting provider may require you to send them a support ticket for this).
- Some providers won't let you configure your reverse DNS (or their feature might be broken...). If you are experiencing issues because of this, consider the following solutions:
- Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://yunohost.org/#/vpn_advantage
- Or it's possible to switch to a different provider
status: ERROR
summary: The reverse DNS is not correctly configured in IPv4. Some emails may fail to get delivered or may get flagged as spam.
3:
details:
- The blacklist reason is: "http://www.barracudanetworks.com/reputation/?pr=1&ip=77.109.97.197"
- After identifying why you are listed and fixed it, feel free to ask for your IP or domaine to be removed on https://barracudacentral.org/rbl/
status: ERROR
summary: Your IP or domain 77.109.97.197 is blacklisted on Barracuda Reputation Block List
4:
details:
- The blacklist reason is: "SPAMRATS IP Addresses See: http://www.spamrats.com/bl?77.109.97.197"
- After identifying why you are listed and fixed it, feel free to ask for your IP or domaine to be removed on http://www.spamrats.com/
status: ERROR
summary: Your IP or domain 77.109.97.197 is blacklisted on SpamRATS! all
3:
description: Services status check
id: services
items:
0:
details: You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart fail2ban' and 'yunohost service log fail2ban').
status: ERROR
summary: Service fail2ban is failed :(
1:
details: You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart ynh-vpnclient' and 'yunohost service log ynh-vpnclient').
status: ERROR
summary: Service ynh-vpnclient is failed :(
2:
details: You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart yunohost-firewall' and 'yunohost service log yunohost-firewall').
status: ERROR
summary: Service yunohost-firewall is failed :(
4:
description: System configurations
id: regenconf
items:
0:
details: This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically... But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf dnsmasq --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf dnsmasq --force'
status: WARNING
summary: Configuration file /etc/resolv.dnsmasq.conf appears to have been manually modified.
1:
details: This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically... But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf ssh --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf ssh --force'
status: WARNING
summary: Configuration file /etc/ssh/sshd_config appears to have been manually modified.
2:
details: This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically... But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf ssl --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf ssl --force'
status: WARNING
summary: Configuration file /usr/share/yunohost/yunohost-config/ssl/yunoCA/openssl.cnf appears to have been manually modified.`
Avec…
# systemctl status fail2ban
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2022-08-29 14:06:17 UTC; 8min ago
Docs: man:fail2ban(1)
Process: 727 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
Process: 854 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
Main PID: 854 (code=exited, status=255/EXCEPTION)
CPU: 2.329s
root@MonServeur:/home/Userssh# systemctl status ynh-vpnclient
● ynh-vpnclient.service - YunoHost VPN Client.
Loaded: loaded (/etc/systemd/system/ynh-vpnclient.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2022-08-29 14:12:58 UTC; 2min 19s ago
Process: 4114 ExecStart=/usr/local/bin/ynh-vpnclient start (code=exited, status=1/FAILURE)
Main PID: 4114 (code=exited, status=1/FAILURE)
CPU: 4.401s
root@MonServeur:/home/Userssh# systemctl status yunohost-firewall
● yunohost-firewall.service - YunoHost Firewall
Loaded: loaded (/lib/systemd/system/yunohost-firewall.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2022-08-29 14:06:25 UTC; 9min ago
Process: 816 ExecStart=/usr/bin/yunohost firewall reload (code=exited, status=1/FAILURE)
Main PID: 816 (code=exited, status=1/FAILURE)
CPU: 3.522s
Je ne sais pas bien par quel bout prendre ces petits soucis.
Si vous avez des pistes, n’hésitez pas !
Merci d’avance !
!