403 Forbidden - You don't have permission to access this resource

Discussions Générales
19

Bonjour, je relance le sujet…

Après un uptime de 11 jours, j’ai à nouveau eu le souci… :sweat_smile:

  • Accès Jeedom via HTTPS => KO

Forbidden
You don’t have permission to access this resource.Server unable to read htaccess file, denying access to be safe

  • Accès Jeedom via HTTP => KO

Forbidden
You don’t have permission to access this resource.Server unable to read htaccess file, denying access to be safe

  • L’accès via HTTP de mon autre ressource (ha-bridge) tournant sur mon RPI ==> KO

ERR_CONNECTION_REFUSED

  • Accès en SSH => KO
$ ssh -vvv hakuna@192.168.X.X
OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/Hakuna/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.X.X is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.X.X [192.168.X.X] port 22.
debug1: Connection established.
debug1: identity file /Users/Hakuna/.ssh/id_rsa type 0
debug1: identity file /Users/Hakuna/.ssh/id_rsa-cert type -1
debug1: identity file /Users/Hakuna/.ssh/id_dsa type -1
debug1: identity file /Users/Hakuna/.ssh/id_dsa-cert type -1
debug1: identity file /Users/Hakuna/.ssh/id_ecdsa type -1
debug1: identity file /Users/Hakuna/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/Hakuna/.ssh/id_ed25519 type -1
debug1: identity file /Users/Hakuna/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/Hakuna/.ssh/id_xmss type -1
debug1: identity file /Users/Hakuna/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
kex_exchange_identification: read: Connection reset by peer

J’ai profité de cette erreur pour faire un hard reboot et en même temps mettre dtoverlay=sdtweak,poll_once

Et je constate déjà une belle diminution du load CPU ! Peut-être que ça va m’aider :crossed_fingers:

Je vais tenter l’upgrade vers Buster dans les prochains jours, pour voir si cela résout le souci…

Bonne journée !

EDIT
Bah ça aura tenu moins de deux heures…
A nouveau la même erreur, et exactement le même comportement si je tente l’accès HTTP, HTTPS ou SSH…