Every day: The server does not have an IPv6 address / Chaque jour : Le serveur ne dispose pas d'une adresse IPv6

Diabolo · March 16, 2025, 3:28pm

What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.0.11
How are you able to access your server: The webadmin
SSH

Describe your issue

English :

Hello

For the past two weeks, I feel like I’ve been looking everywhere for help with my problem without finding a solution or any direction. Note: I’m proficient in hardware, Windows, and IPv4; but I’m a beginner with VPS, Linux, Yunohost, and IPv6.

I installed Yunohost on an Infomaniak Public Cloud running OpenStack with the following resources: a4-ram8-disk20-perf1 (4 cores, 8GB RAM, 20GB storage).

My domain and DNS records are with OVH.

I’ve been installing and using the server in production for a week, after a week of testing. I monitor the diagnostics and check for updates regularly.

Since day one, every day, at some point during the diagnostics, I find the IPv6 service (or connection) going down, without me doing anything in particular. I have no explanation. I restarted the server via Tools > Restart and everything returned to normal for about 24 hours. So for the past 15 days, I’ve been experiencing the same problem every day

You’ll find the diagnostic logs from when I noticed it had crashed again last night around 3:20 AM (UTC+1) plus the nginx logs from today.

Thank you in advance for your assistance. Let me know if you need any further information.

Long live Yunohost, which I think is super

Share relevant logs or error messages

Diagnostic logs : https://paste.yunohost.org/raw/ivojezebob

Nginx logs : hastebin

Français :

Bonjour

Depuis 2 semaines j’ai le sentiment d’avoir cherché un peu partout de l’aide concernant mon problème sans avoir trouvé de solution ni de piste de réflexion. NB : Je suis compétent en hardware, Windows et IPv4 ; mais je suis débutant en VPS, Linux, Yunohost et IPv6.

Mon domaine et mes enregistrements DNS sont chez OVH.

J’ai installé Yunohost sur un Public Cloud Infomaniak sous OpenStack avec les ressources a4-ram8-disk20-perf1 (4 cœurs, 8Go RAM, 20Go stockage).

Installation et utilisation du serveur en production depuis une semaine, après une semaine de tests. Je contrôle le diagnostic et recherche les mises à jours régulièrement.

Depuis le premier jour, tous les jours, à partir d’un moment lors du diagnostic je me retrouve avec le service (ou la connexion) IPv6 qui tombe en rade, sans que je ne fasse quoi que ce soit de particulier. Je n’ai aucune explication. Je redémarre le serveur via Outils > Redémarrer et tout revient dans l’ordre pour plus ou moins 24h. Donc depuis 15 jours je rencontre le même problème tous les jours

Vous trouverez les logs de diagnostics quand je me suis aperçu que ça avait encore buggé cette nuit vers 3h20 (UTC+1) + ceux de nginx aujourd’hui.

En vous remerciant par avance pour votre assistance, dites-moi si vous aviez besoin d’autres informations.

Vive Yunohost que je trouve super

Share relevant logs or error messages

Diagnostic logs : https://paste.yunohost.org/raw/ivojezebob

Nginx logs : hastebin

Diabolo · March 17, 2025, 11:32am

English :

This morning rebelote, and I don’t seem to find anything in the logs.

The only thing I can say is that I have the impression that IPv6 crashes every 24 hours after a reboot. I don’t know if this could happen after running a routine?

Thank you in advance for your help

DNS cheker : DNS Checker - DNS Check Propagation Tool
Diagnostic logs : https://paste.yunohost.org/raw/oducatebed
dnsmasq : hastebin
nginx : hastebin
yunomdns : hastebin

Français :

Rebelote ce matin, et j’ai l’impression de ne rien trouver dans les logs.

La seule chose que je peux dire, c’est que j’ai l’impression que c’est autour de 24h après un redémarrage que l’IPv6 tombe en rade, je ne sais pas si ça pourrait survenir à la suite de l’exécution d’une routine ?

En vous remerciant par avance pour votre aide

DNS cheker : DNS Checker - DNS Check Propagation Tool
Diagnostic logs : https://paste.yunohost.org/raw/oducatebed
dnsmasq : hastebin
nginx : hastebin
yunomdns : hastebin

Diabolo · March 20, 2025, 2:20pm

I’m sorry to bring this up again. I’m not trying to push or pressure you, but rather to provide some leads if they can help resolve the issue.

I don’t know if this would help, and I have no idea what else I could do to investigate.

I just installed Debian 12, Yunohost, Mailman3, Collabora Online, and Uptime Kuma.

When IPv6 is working and I query $ ip a, I get:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether fa:16:3e:f3:1c:9c brd ff:ff:ff:ff:ff:ff
    inet 37.156.46.63/24 metric 100 brd 37.156.46.255 scope global dynamic enp3s0
       valid_lft 83670sec preferred_lft 83670sec
    inet6 2001:1600:16:10::603/128 scope global dynamic noprefixroute
       valid_lft 83671sec preferred_lft 83671sec
    inet6 fe80::f816:3eff:fef3:1c9c/64 scope link
       valid_lft forever preferred_lft forever

When IPv6 no longer works (after 24 hours of server activity), I query $ ip a and I get:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether fa:16:3e:f3:1c:9c brd ff:ff:ff:ff:ff:ff
    inet 37.156.46.63/24 metric 100 brd 37.156.46.255 scope global dynamic enp3s0
       valid_lft 80458sec preferred_lft 80458sec
    inet6 fe80::f816:3eff:fef3:1c9c/64 scope link
       valid_lft forever preferred_lft forever

I restart the server using the function in Yunohost, and IPv6 works again for 24 hours

Je suis désolé de revenir sur le sujet, ce n’est pas pour insister ni pour mettre la pression mais pour apporter des pistes si ça peut aider à la résolution.

Je ne sais pas si ça pourrait aider, et je ne sais pas du tout ce que je pourrais faire de plus pour investiguer.

J’ai juste installé Debian 12, Yunohost, Mailman3, Collabora Online et Uptime Kuma.

Quand IPv6 fonctionne et que je questionne $ ip a j’obtiens :

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether fa:16:3e:f3:1c:9c brd ff:ff:ff:ff:ff:ff
    inet 37.156.46.63/24 metric 100 brd 37.156.46.255 scope global dynamic enp3s0
       valid_lft 83670sec preferred_lft 83670sec
    inet6 2001:1600:16:10::603/128 scope global dynamic noprefixroute
       valid_lft 83671sec preferred_lft 83671sec
    inet6 fe80::f816:3eff:fef3:1c9c/64 scope link
       valid_lft forever preferred_lft forever

Quand IPv6 ne fonctionne plus (au bout de 24h d’activité du serveur) je questionne $ ip a et j’obtiens :

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether fa:16:3e:f3:1c:9c brd ff:ff:ff:ff:ff:ff
    inet 37.156.46.63/24 metric 100 brd 37.156.46.255 scope global dynamic enp3s0
       valid_lft 80458sec preferred_lft 80458sec
    inet6 fe80::f816:3eff:fef3:1c9c/64 scope link
       valid_lft forever preferred_lft forever

Je redémarre le serveur avec la fonction dans Yunohost et IPv6 refonctionne pour 24h

lab.8916100448256 · March 20, 2025, 8:44pm

Try to use a static ip address configuration, maybe?

Diabolo · March 20, 2025, 10:07pm

Good evening @lab.8916100448256,

Thank you very much for the reply and the tip

If I learn, I know how to reuse and adapt, but I’m a Linux novice at the moment

The day before yesterday, I learned about the ifconfig command, but I couldn’t use it. Yesterday, I learned that I now have to use ip. That’s how I was able to provide the information this morning.

The Yunohost documentation¹ says to modify the /etc/network/interfaces file.

But when I browse the folder, I only see three subfolders: if-down.d / if-pre-up.d / if-up.d

In my Infomaniak interface, in the Network section, I find: ext-net1-v6subnet1 2001:1600:16:10::/64 IPv6 2001:1600:16:10::1

The IPv6 address mentioned is shorter than the public address to join my Yunohost server: 2001:1600:16:10::603/128

If I’m not mistaken, I should add:

iface enp0s3 inet6 static
address 2001:1600:16:10::603
netmask /128
post-up /sbin/ip -6 route add 2001:1600:16:10::1 dev enp0s3
post-up /sbin/ip -6 route add default via 2001:1600:16:10::1 dev enp0s3
pre-down /sbin/ip -6 route del default via 2001:1600:16:10::1 dev enp0s3
pre-down /sbin/ip -6 route del 2001:1600:16:10::1 dev enp0s3

Is that right? But now I don’t know where the file to modify is

Thanks in advance for the help and sorry for the beginner that I am

¹ I found a bad link on the French documentation page: Configuration de l'IPv6 | Yunohost Documentation
Configure the DNS server
here: YunoHost: garden your own piece of the Internet!
should instead redirect here in my opinion: Configuration de la zone DNS | Yunohost Documentation
I tried to do it myself so as not to disturb, I connected to GitHub, but after that I don’t know whether to Fork this repository and edit the file or Edit in place and I especially don’t want to break anything in the community

rodinux · March 20, 2025, 10:43pm

Thanks for the broken links… Don’t be affraid, you can contribute it will just open a PR… I have done one for this suggestion…

rodinux · March 20, 2025, 10:46pm

Diabolo:

The IPv6 address mentioned is shorter than the public address to join my Yunohost server: 2001:1600:16:10::603/128

If I’m not mistaken, I should add:
iface enp0s3 inet6 static
address 2001:1600:16:10::603
netmask /128
post-up /sbin/ip -6 route add 2001:1600:16:10::1 dev enp0s3
post-up /sbin/ip -6 route add default via 2001:1600:16:10::1 dev enp0s3
pre-down /sbin/ip -6 route del default via 2001:1600:16:10::1 dev enp0s3
pre-down /sbin/ip -6 route del 2001:1600:16:10::1 dev enp0s3

This was a topic for a vps on ovh… but don’t know if it works also on a infomaniak server

jarod5001 · March 20, 2025, 10:47pm

Can you share its content?

Diabolo · March 20, 2025, 11:00pm

Hello @rodinux and @jarod5001, thanks for you assistance

$ cd /etc/network/interfaces
-bash: cd: /etc/network/interfaces: No such file or directory
$ cd /etc/network/
$ ls
if-down.d  if-pre-up.d  if-up.d
$

jarod5001 · March 20, 2025, 11:16pm

Oh, what is the output of these 3 commands?

# Check if Netplan is Used
ls /etc/netplan/

# Check if NetworkManager is Used
nmcli device status

# Check for Systemd-Networkd
systemctl status systemd-networkd

rodinux · March 20, 2025, 11:16pm

ok, do you have something also in /etc/netplan ? It a new protocol easy also to test

Diabolo · March 20, 2025, 11:21pm

Note that currently IPv6 is already dysfunctional, I wait until night to restart the server without disturbing users.

$ ls /etc/netplan/
50-cloud-init.yaml
$ nmcli device status
-bash: nmcli: command not found
$ systemctl status systemd-networkd
● systemd-networkd.service - Network Configuration
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-03-19 02:03:40 UTC; 1 day 21h ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   Main PID: 480
     Status: "Processing requests..."
      Tasks: 1 (limit: 9481)
     Memory: 3.1M
        CPU: 1.195s
     CGroup: /system.slice/systemd-networkd.service
             └─480 /lib/systemd/systemd-networkd

Warning: some journal files were not opened due to insufficient permissions.
$

rodinux · March 20, 2025, 11:23pm

you can first use root account for permissions

sudo -i
cat /etc/netplan/50-cloud-init.yaml

jarod5001 · March 20, 2025, 11:24pm

And ls /etc/systemd/network

Diabolo · March 20, 2025, 11:25pm

# cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        enp3s0:
            accept-ra: true
            dhcp4: true
            dhcp6: true
            match:
                macaddress: fa:16:3e:f3:1c:9c
            set-name: enp3s0

Diabolo · March 20, 2025, 11:27pm

$ ls /etc/systemd/network
Nothing happens

jarod5001 · March 20, 2025, 11:28pm

Sorry cat /lib/systemd/system/systemd-networkd.service

jarod5001 · March 20, 2025, 11:31pm

And ls /run/systemd/network/

If you find any file with enp3s0, share its content

Diabolo · March 20, 2025, 11:44pm

$ cat /lib/systemd/system/systemd-networkd.service
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Network Configuration
Documentation=man:systemd-networkd.service(8)
Documentation=man:org.freedesktop.network1(5)
ConditionCapability=CAP_NET_ADMIN
DefaultDependencies=no
# systemd-udevd.service can be dropped once tuntap is moved to netlink
After=systemd-networkd.socket systemd-udevd.service network-pre.target systemd-sysusers.service systemd-sysctl.service
Before=network.target multi-user.target shutdown.target initrd-switch-root.target
Conflicts=shutdown.target initrd-switch-root.target
Wants=systemd-networkd.socket network.target

[Service]
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW
BusName=org.freedesktop.network1
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW
DeviceAllow=char-* rw
ExecStart=!!/lib/systemd/systemd-networkd
ExecReload=networkctl reload
FileDescriptorStoreMax=512
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
ProtectProc=invisible
ProtectClock=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectSystem=strict
Restart=on-failure
RestartKillSignal=SIGUSR2
RestartSec=0
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 AF_PACKET
RestrictNamespaces=yes
RestrictRealtime=yes
RestrictSUIDSGID=yes
RuntimeDirectory=systemd/netif
RuntimeDirectoryPreserve=yes
SystemCallArchitectures=native
SystemCallErrorNumber=EPERM
SystemCallFilter=@system-service
Type=notify
User=systemd-network
WatchdogSec=3min

[Install]
WantedBy=multi-user.target
Also=systemd-networkd.socket
Alias=dbus-org.freedesktop.network1.service

# The output from this generator is used by udevd and networkd. Enable it by
# default when enabling systemd-networkd.service.
Also=systemd-network-generator.service

# We want to enable systemd-networkd-wait-online.service whenever this service
# is enabled. systemd-networkd-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=systemd-networkd-wait-online.service

$ ls /run/systemd/network/
10-netplan-enp3s0.link  10-netplan-enp3s0.network

10-netplan-enp3s0.link

[Match]
PermanentMACAddress=fa:16:3e:f3:1c:9c

[Link]
Name=enp3s0
WakeOnLan=off

10-netplan-enp3s0.network

[Match]
PermanentMACAddress=fa:16:3e:f3:1c:9c
Name=enp3s0

[Network]
DHCP=yes
LinkLocalAddressing=ipv6
IPv6AcceptRA=yes

[DHCP]
RouteMetric=100
UseMTU=true

jarod5001 · March 21, 2025, 12:11am

Et journalctl -u systemd-networkd | grep DHCPv6