# Install - Raspberry Pi - Nging broken - 97: Address family not supported by protocol

**URL:** https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680
**Category:** Support
**Tags:** french
**Created:** [May 1, 2022, 8:49am UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680 "2022-05-01T08:49:26Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![claveryu](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/c/bcef8e/32.png) [@claveryu](https://forum.yunohost.org/u/claveryu)
#### Post date: [May 1, 2022, 8:49am UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680/1 "2022-05-01T08:49:26Z")

</div>

### My YunoHost server

**Hardware:** Raspberry Pi 3 B at home (Linux my.test 5.10.11-v7+ #1399 SMP Thu Jan 28 12:06:05 GMT 2021 armv7l GNU/Linux)  
**YunoHost version:** yunohost:  
repo: stable  
version: 4.3.6.3  
yunohost-admin:  
repo: testing  
version: 4.3.4.1  
moulinette:  
repo: stable  
version: 4.3.3.1  
ssowat:  
repo: stable  
version: 4.3.3.1  
**I have access to my server :** Through SSH / direct access via keyboard / screen  
**Are you in a special context or did you perform some particular tweaking on your YunoHost instance ?** : yes  
**If yes, please explain:** boot on sd card, root on external hard drive (usb)

Hello,

I tried a new fresh install with an external usb harddrive, after postinstall, yunohost update/upgrade I have an issue with Nginx :

```auto
nginx: 
  configuration: broken
  configuration-details: 
    - 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
  description: Serves or provides access to all the websites hosted on your server
  last_state_change: 2022-05-01 09:22:50
  start_on_boot: enabled
  status: failed
```

```auto
root@serv:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 39G 2.3G 35G 7% /
devtmpfs 430M 0 430M 0% /dev
tmpfs 463M 0 463M 0% /dev/shm
tmpfs 463M 6.3M 456M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 463M 0 463M 0% /sys/fs/cgroup
/dev/sda1 253M 96M 157M 38% /boot
tmpfs 93M 0 93M 0% /run/user/0
root@serv:~# 
```

```auto
root@serv:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk 
├─sda1 8:1 0 256M 0 part /boot
├─sda2 8:2 0 39.1G 0 part /
└─sda3 8:3 0 1.9G 0 part 
mmcblk0 179:0 0 14.9G 0 disk 
├─mmcblk0p1 179:1 0 256M 0 part 
└─mmcblk0p2 179:2 0 14.6G 0 part 
root@serv:~#
```

```auto
root@serv:/boot# journalctl -p err
-- Logs begin at Sun 2022-05-01 09:22:04 BST, end at Sun 2022-05-01 09:39:01 BST. --
May 01 09:22:04 serv.test kernel: sd 0:0:0:0: [sda] No Caching mode page found
May 01 09:22:04 serv.test kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May 01 09:22:05 serv.test systemd-udevd[176]: could not open moddep file '/lib/modules/5.10.11-v7+/modules.dep.bin'
May 01 09:22:05 serv.test systemd-udevd[176]: could not open moddep file '/lib/modules/5.10.11-v7+/modules.dep.bin'
May 01 09:22:06 serv.test systemd-udevd[176]: could not open moddep file '/lib/modules/5.10.11-v7+/modules.dep.bin'
May 01 09:22:06 serv.test systemd-udevd[182]: sda: Conflicting device node '/dev/mmcblk0' found, link to '/dev/sda' will not be create
May 01 09:22:06 serv.test systemd-udevd[180]: sda2: Conflicting device node '/dev/mmcblk0p2' found, link to '/dev/sda2' will not be cr
May 01 09:22:06 serv.test systemd-udevd[182]: sda1: Conflicting device node '/dev/mmcblk0p1' found, link to '/dev/sda1' will not be cr
May 01 09:22:08 serv.test systemd-udevd[184]: sda1: Conflicting device node '/dev/mmcblk0p1' found, link to '/dev/sda1' will not be cr
May 01 09:22:12 serv.test dhcpcd[350]: ipv6_addaddr1: Operation not supported
May 01 09:22:12 serv.test dhcpcd[350]: ipv6nd_startrs1: Address family not supported by protocol
May 01 09:22:14 serv.test systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
May 01 09:22:20 serv.test ntpd[589]: restrict: ignoring line 40, mask '::' unusable.
May 01 09:22:46 serv.test dovecot[861]: master: Error: socket() failed: Address family not supported by protocol
May 01 09:22:46 serv.test dovecot[861]: master: Error: service(managesieve-login): listen(::, 4190) failed: Address family not support
May 01 09:22:46 serv.test dovecot[861]: master: Error: socket() failed: Address family not supported by protocol
May 01 09:22:46 serv.test dovecot[861]: master: Error: service(imap-login): listen(::, 143) failed: Address family not supported by pr
May 01 09:22:46 serv.test dovecot[861]: master: Error: socket() failed: Address family not supported by protocol
May 01 09:22:46 serv.test dovecot[861]: master: Error: service(imap-login): listen(::, 993) failed: Address family not supported by pr
May 01 09:22:46 serv.test dovecot[861]: master: Fatal: Failed to start listeners
May 01 09:22:50 serv.test systemd[1]: Failed to start YunoHost Firewall.
May 01 09:22:50 serv.test systemd[1]: Failed to start A high performance web server and a reverse proxy server.
```

Thnak’s for advices and help !

---

<div class="post-metadata">

### Author: ![rungeard](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rungeard/32/4371_2.png) [@rungeard](https://forum.yunohost.org/u/rungeard)
#### Post date: [May 1, 2022, 3:11pm UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680/2 "2022-05-01T15:11:36Z")

</div>

> [@claveryu](#):
>
> boot on sd card, root on external hard drive (usb)

Did you try not to use the sd card and to boot directly on the external hard drive ?

---

<div class="post-metadata">

### Author: ![claveryu](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/c/bcef8e/32.png) [@claveryu](https://forum.yunohost.org/u/claveryu)
#### Post date: [May 1, 2022, 3:53pm UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680/3 "2022-05-01T15:53:34Z")

</div>

Hello,

I think it’s not possible with Pi 3 B

---

<div class="post-metadata">

### Author: ![rungeard](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rungeard/32/4371_2.png) [@rungeard](https://forum.yunohost.org/u/rungeard)
#### Post date: [May 1, 2022, 4:05pm UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680/4 "2022-05-01T16:05:44Z")

</div>

> [@claveryu](#):
>
> I think it’s not possible with Pi 3 B

It’s possible !

> **[Booting Raspberry Pi 3 B With a USB Drive](https://www.instructables.com/Booting-Raspberry-Pi-3-B-With-a-USB-Drive/)**
>
> Booting Raspberry Pi 3 B With a USB Drive: The Raspberry Pi 3 B can be booted with a compatible thumb drive without spending any money!
> Note: The Raspberry Pi 3 B+ can be USB booted out-of-the-box.

---

<div class="post-metadata">

### Author: ![system](https://forum.yunohost.org/uploads/default/original/2X/f/f59fe8e3ee6b100b4f574d30d6e30479c68b89f0.png) [@system](https://forum.yunohost.org/u/system)
#### Post date: [May 16, 2022, 4:06pm UTC](https://forum.yunohost.org/t/install-raspberry-pi-nging-broken-97-address-family-not-supported-by-protocol/19680/5 "2022-05-16T16:06:04Z")

</div>

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