Interface Web inaccessible

Mon serveur YunoHost

**Matériel: Raspberry Pi à la maison /
**Version de YunoHost: 11.0.11 (stable)
J’ai accès à mon serveur : En SSH | En direct avec un clavier/écran | …
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non

Description du problème

Bonjour, voilà, mon interface n’est pas joignable. Que je tape mon nom de domaine, l’IP 192.168.x.x ou bien yunohost.local, ça ne donne que ceci:

“La connexion a échoué
Une erreur est survenue pendant une connexion à teneriffe.nohost.me.
Le site est peut-être temporairement indisponible ou surchargé. Réessayez plus tard ;
Si vous n’arrivez à naviguer sur aucun site, vérifiez la connexion au réseau de votre ordinateur ;
Si votre ordinateur ou votre réseau est protégé par un pare-feu ou un proxy, assurez-vous que Firefox est autorisé à accéder au Web.”

Or je n’ai ni parefeu, ni proxy, mon VPN est déconnecté, j’ai enlevé toute les extension de mon firefox, de toute manière ça ne marche pas non plus avec Ungoogled Chromium.
Par contre j’arrive très bien à me connecter à mon Yunohost en SSH en admin, ainsi qu’avec un écran directement branché sur mon Raspberry Pi 4. Mais je ne suis pas fort du tout en lignes de commande et ai vraiment besoin de l’interface.
J’ai vérifié mes redirection de ports, mon DNS reverse, tout est bien. Alors je ne comprend pas pourquoi je n’ai plus accès à l’interface web, que ce soit avec mon ordinateur ou avec mon smartphone., c’est le même message d’échec.

Merci de votre aide précieuse
Christophe

Du coup est-ce que tu peux expliquer un peu plus le contexte, est-ce qu’il s’agit d’une nouvelle installation, ou bien est-ce que quelque chose a récemment changé sur ton installation …

Aussi, que raconte l’outil de diagnostic ?

Salut Aleks.
Pas de nouvelle installation, le seul truc qui a changé (je m’en suis aperçu en checkant mes redirections de ports) c’est l’accès à mon machinBox OS, iels avaient changé l’URL sans me le dire, mais d’après leurs dires ça faisaient plusieurs mois que ça avait changé, or je ne me souviens pas que ça fait si longtemps que j’ai ce problème d’accès à mon interface web.

Pour ce qui est du diagnostic, puisque je n’ai pas accès à l’interface, je tape ça dans mon terminal, mais ça me donne la suite:

"admin@teneriffe:~ $ sudo yunohost tools diagnosis | yunopaste

Invalid usage: No input is provided.
Usage: /usr/bin/yunopaste [OPTION]…
Read from input stream and paste the data to the YunoHost
Haste server.
For example, to paste the output of the YunoHost diagnosis, you
can simply execute the following:
yunohost diagnosis show | /usr/bin/yunopaste
It will return the URL where you can access the pasted data.
Options:
-h, --help show this help message and exit
usage: yunohost tools {adminpw,maindomain,postinstall,update,upgrade,shell,shutdown,reboot,regen-conf,versions,migrations}

[-h]
yunohost tools: error: argument {adminpw,maindomain,postinstall,update,upgrade,shell,shutdown,reboot,regen-conf,versions,migrations}: invalid choice: ‘diagnosis’ (choose from ‘adminpw’, ‘maindomain’, ‘postinstall’, ‘update’, ‘upgrade’, ‘shell’, ‘shutdown’, ‘reboot’, ‘regen-conf’, ‘versions’, ‘migrations’)"

Alors je tape ce qu’iels ont écris, mais ça ne me dit que ça:

"admin@teneriffe:~ $ sudo yunohost diagnosis show | /usr/bin/yunopaste

Invalid usage: No input is provided.
Usage: /usr/bin/yunopaste [OPTION]…
Read from input stream and paste the data to the YunoHost
Haste server.
For example, to paste the output of the YunoHost diagnosis, you
can simply execute the following:
yunohost diagnosis show | /usr/bin/yunopaste
It will return the URL where you can access the pasted data.
Options:
-h, --help show this help message and exit
Warning: unable to retrieve string to translate with key ‘d’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘i’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘g’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘n’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘o’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘s’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘i’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘s’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘m’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘i’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘l’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key '
’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘q’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘u’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘e’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘u’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘e’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘u’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘n’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘v’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘i’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘l’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘b’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘l’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘e’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key '
’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘d’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘e’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘t’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘a’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘i’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘l’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Warning: unable to retrieve string to translate with key ‘s’ for default locale ‘locales/en.json’ file (don’t panic this is just a warning)
Traceback (most recent call last):
File “/usr/bin/yunohost”, line 71, in
yunohost.cli(
File “/usr/lib/python3/dist-packages/yunohost/init.py”, line 25, in cli
ret = moulinette.cli(
File “/usr/lib/python3/dist-packages/moulinette/init.py”, line 111, in cli
Cli(
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 521, in run
pretty_print_dict(ret)
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 183, in pretty_print_dict
pretty_print_dict({key: value}, depth + 1)
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 176, in pretty_print_dict
pretty_print_dict(v, depth + 1)
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 183, in pretty_print_dict
pretty_print_dict({key: value}, depth + 1)
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 176, in pretty_print_dict
pretty_print_dict(v, depth + 1)
File “/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py”, line 191, in pretty_print_dict
print(“{:s}{}: {}”.format(" " * depth, k, v))
BrokenPipeError: [Errno 32] Broken pipe"

Je sais, c’est illisible, mais je ne vois pas comment récupérer l’URL…

Et sinon sur mon installation, rien de nouveau, puisque je me suis rendu compte que mon Raspberry Pi 4 modèle B, qui devrait être un ARMv8 (64bit), n’est qu’un ARMv7l (32bit) alors je ne pouvais plus mettre à jour mon NextCloud. Mais ça faisait déjà longtemps que c’était cette situation bloquée quand mon interface a planté.

Mokay on va plutôt faire: yunohost diagnosis show --issues --share --human-readable

Alors voilà; https://paste.yunohost.org/raw/zanotineni
merci beaucoup

Moui du coup nginx est dans les choux …

On devrait commencer par regarder ce que raconte nginx -t,

et si il semble happy: systemctl restart nginx puis systemctl status nginx

et si nginx est toujours dans les choux, regarder journalctl -u nginx -n 50 --no-pager --no-hostname

Alors déjà ça:

admin@teneriffe:~ $ sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

admin@teneriffe:~ $ sudo systemctl restart nginx
Job for nginx.service failed because the control process exited with error code.
See “systemctl status nginx.service” and “journalctl -xe” for details.

Après en faisant ce qu’il demandent j’attends que ça revienne à admin, mais ça a l’air bloqué là:

admin@teneriffe:~ $ sudo systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:>
Active: failed (Result: exit-code) since Mon 2023-02-13 03:11:35 CET; 41s >
Docs: man:nginx(8)
Process: 7152 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_proce>
CPU: 358ms

Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: Starting A high performance web>
Feb 13 03:11:35 teneriffe.nohost.me nginx[7152]: nginx: [emerg] socket() [::]:8>
Feb 13 03:11:35 teneriffe.nohost.me nginx[7152]: nginx: configuration file /etc>
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: nginx.service: Control process >
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: nginx.service: Failed with resu>
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: Failed to start A high performa>
lines 1-13/13 (END)

Faut-il que je tape quelquechose?

● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-02-13 03:11:35 CET; 41s ago
Docs: man:nginx(8)
Process: 7152 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 358ms

Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: Starting A high performance web server and a reverse proxy server…
Feb 13 03:11:35 teneriffe.nohost.me nginx[7152]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Feb 13 03:11:35 teneriffe.nohost.me nginx[7152]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 13 03:11:35 teneriffe.nohost.me systemd[1]: Failed to start A high performance web server and a reverse proxy server.
~
~
~
~
~
~
~
~
~
~
lines 1-13/13 (END)

avec la dernière ligne qui clignote en surlignage blanc.
et ce répété plein de fois

Moui du coup nginx n’aime pas le morceau où il est censé écouter en IPv6 … Ça ressemble à un truc où IPv6 a été complètement désactivé sur le système, même en local (i.e. des fois ta machine n’a pas d’IPv6 global ni même locale, mais souvent il y a quand même de l’IPv6 “en interne” dans la machine)

Est-ce que ça te parle ?

avant de parler ipv6 je t’envoie ceci, j’ai fermé le terminal bloqué et ai tapé la fin de ta proposition:

admin@teneriffe:~ $ sudo journalctl -u nginx -n 50 --no-pager --no-hostname
– Journal begins at Thu 2022-10-06 06:07:55 CEST, ends at Mon 2023-02-13 03:52:20 CET. –
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/cryptpad.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/funkwhale.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/funkwhale.teneriffe.nohost.me/crt.pem”
– Boot c12dd4eb8c3b4b328bdf886cfecaa84c –
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/archetsdumonde.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/archetsdumonde.teneriffe.nohost.me/crt.pem”
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/roundcube.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/roundcube.teneriffe.nohost.me/crt.pem”
– Boot c12dd4eb8c3b4b328bdf886cfecaa84c –
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/cryptpad.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/cryptpad.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/funkwhale.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/funkwhale.teneriffe.nohost.me/crt.pem”
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[643]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/teneriffe.nohost.me/crt.pem”
– Boot c12dd4eb8c3b4b328bdf886cfecaa84c –
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/roundcube.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/roundcube.teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/teneriffe.nohost.me/crt.pem”
Feb 12 22:17:10 nginx[652]: nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “r3.o.lencr.org” in the certificate “/etc/yunohost/certs/teneriffe.nohost.me/crt.pem”
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 12 22:17:11 nginx[643]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
– Boot 56be103c822a4bb79998581f3b14d408 –
Feb 12 22:17:11 nginx[647]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 12 22:17:11 nginx[643]: nginx: configuration file /etc/nginx/nginx.conf test failed
– Boot 56be103c822a4bb79998581f3b14d408 –
Feb 12 22:17:11 nginx[647]: nginx: configuration file /etc/nginx/nginx.conf test failed
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 12 22:17:11 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 12 22:17:11 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 12 22:17:11 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
– Boot 56be103c822a4bb79998581f3b14d408 –
Feb 12 22:17:11 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 12 22:17:11 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 12 22:17:11 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
– Boot c12dd4eb8c3b4b328bdf886cfecaa84c –
Feb 12 22:17:11 nginx[652]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Feb 12 22:17:11 nginx[652]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 12 22:17:11 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 12 22:17:11 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 12 22:17:11 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
– Boot dc18901b66914a088fc6b457d26942cf –
Feb 13 02:52:32 systemd[1]: Starting A high performance web server and a reverse proxy server…
Feb 13 02:52:32 nginx[6480]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Feb 13 02:52:32 nginx[6480]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 13 02:52:32 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 13 02:52:32 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 13 02:52:32 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 13 02:57:40 systemd[1]: Starting A high performance web server and a reverse proxy server…
Feb 13 02:57:41 nginx[6645]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Feb 13 02:57:41 nginx[6645]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 13 02:57:41 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 13 02:57:41 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 13 02:57:41 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 13 03:11:35 systemd[1]: Starting A high performance web server and a reverse proxy server…
Feb 13 03:11:35 nginx[7152]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Feb 13 03:11:35 nginx[7152]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 13 03:11:35 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Feb 13 03:11:35 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Feb 13 03:11:35 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
admin@teneriffe:~ $

Alors pour l’IPv6 ben oui moi je milite pour la fin de l’IPv4, mais avec ma freebox c’est compliqué. Voilà ce que m’affiche “configuration IPv6” dans ma FreeBox OS:

Comme expliqué je ne parle pas de si il y a ou non de l’IPv6 sur la réseau local, je parle de si tu aurais manuellement désactivé à un moment IPv6 complètement dans la machine

Bonjour Aleks,
non j’ai su dans les admindocs Yunohost que l’IPv6 n’était pas possible avec l’FTTH de Free. Alors j’ai, dès le début, ignoré ce message d’erreur dans Diagnosis, c’est à dire que je n’en tiens pas compte. Mais je n’ai pas désactivé l’IPv6 elle-même. Je ne saurais d’ailleurs pas comment faire.
Et ça marchait bien jusque là.
Je tape ifconfig sur mon ordi je vois bien une IPv6 pour mon ordi, si je le fais en ssh pour mon raspberry je ne trouve pas d’IPv6…

Dois-je activer le serveur DHCPv6 dans ma Freebox OS?
J’ai fait une mise à jour de mon Yunohost en SSH, ça n’a rien changé… toujours inaccessible avec mon navigateur.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.