On NS 7.7 we had an network issue on Raspberry PI 4’s which wasn’t solved.
The problem was without Network Manager enabled it did not wait for the network interface to come ready and as a consequence netherserver-init began without an ip obtained by DHCP. (see issue on bug tracker)
At least in my setup it works now, this being such an critical error i’d like to have confirmation
Test procedure:
Flash the test-image and boot it on a Raspberry PI 4
Check if an IP-adress is obtained by DHCP: ip a IF SO
Prepare for nethserver-init by creating the first-boot flag ( touch /var/spool/first-boot )
Reboot and check IP again and it should initialize nethserver-7.8.2003 as usual ( journalctl -f )
Great work!
Tested with a LAN connection and the IP was there after booting the image the first time and after reboot nethserver-init worked as expected. There were no errors in /var/log/messages.
Thank you @mrmarkuz, this makes me very ! (spend hours on this issue )
Do not know if this is the issue: with Firefox I need to remove excepted certificates for the same board (macadress https://ip:port) regularly. Firefox can not handle an infinitive amount of saved certificates for the same url.
EDIT:
Well checking the test-install this morning found this, although is did not cause a issue you described:
You have mail in /var/spool/mail/root
# cat /var/spool/mail/root
From root@rpi4.xxxxx.nl Tue May 5 23:34:35 2020
Return-Path: <root@rpi4.xxxxx.nl>
X-Original-To: root@localhost
Delivered-To: root@localhost.xxxxx.nl
Received: by rpi4.xxxxx.nl (Postfix, from userid 0)
id 237FEA989; Tue, 5 May 2020 23:34:35 +0200 (CEST)
Date: Tue, 05 May 2020 23:34:35 +0200
To: root@localhost.xxxxx.nl
Subject: rpi4.xxxxx.nl certificate has been generated
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20200505213435.237FEA989@rpi4.xxxxx.nl>
From: root@rpi4.xxxxx.nl (root)
rpi4.xxxxx.nl certificate has been automatically generated
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1588714474 (0x5eb1dbea)
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=NethServer, O=Example Org, ST=SomeState, OU=Main/emailAddress=root@rpi4.xxxxx.nl, C=--, L=Hometown
Validity
Not Before: May 5 21:34:34 2020 GMT
Not After : May 3 21:34:34 2030 GMT
Subject: CN=NethServer, O=Example Org, ST=SomeState, OU=Main/emailAddress=root@rpi4.xxxxx.nl, C=--, L=Hometown
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:d8:7b:41:50:aa:62:2e:aa:3f:81:89:58:71:6c:
bb:c5:c3:a9:6e:67:70:31:ed:57:41:22:80:3e:4a:
1b:4d:a6:2d:cb:fd:4f:cd:3c:0e:39:fd:71:f1:5d:
91:e8:50:c9:32:18:8e:40:ed:ae:8a:fa:54:c0:43:
95:52:8c:34:2a:e9:8f:d5:b7:34:71:74:84:0c:42:
dc:43:46:33:f5:82:6a:bc:c3:3f:81:c0:5d:33:d5:
97:0c:2c:33:7d:a7:fe:a1:bd:8f:e0:bb:e4:d8:7b:
55:5e:ac:fb:2e:82:f8:7f:bb:74:62:3d:95:ce:d9:
93:4c:2b:df:bc:a9:aa:14:e4:9c:e4:cb:37:d0:0c:
bf:c1:84:2e:a3:5d:0e:20:82:4a:d6:f1:ab:fc:82:
a3:12:4c:19:ea:ee:d6:4f:56:9b:55:0d:df:cb:07:
35:4c:18:1e:76:d9:5e:ca:3a:8d:ad:ae:c1:b3:4b:
ae:16:4a:9e:b8:57:94:43:c6:46:04:79:b7:f8:dd:
39:3d:c7:85:53:fe:a9:86:41:d2:d5:f7:06:61:e8:
1a:a5:87:ef:ca:9b:2a:cc:7d:8a:1a:58:30:21:28:
94:f1:20:8e:be:31:6b:79:74:61:c4:87:30:e4:f5:
a3:16:0f:e5:33:c9:2c:87:89:ee:d2:25:b3:6c:6b:
b7:97
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier:
D6:1F:3D:61:34:83:89:CD:FC:01:A2:BE:A9:62:A8:7A:9B:66:A2:64
X509v3 Authority Key Identifier:
keyid:D6:1F:3D:61:34:83:89:CD:FC:01:A2:BE:A9:62:A8:7A:9B:66:A2:64
X509v3 Basic Constraints:
CA:TRUE
Signature Algorithm: sha256WithRSAEncryption
bc:c7:46:08:40:04:9a:c7:ad:a5:fd:85:e0:d3:4e:f2:cf:66:
7b:5b:e7:ba:96:9c:fd:2e:ad:bf:03:62:57:1b:36:3b:08:e1:
9b:46:b1:e8:09:57:7e:3c:e0:a7:99:80:67:4e:f2:60:71:d9:
49:7c:04:f9:c8:1a:92:85:ce:6c:d2:e1:81:ec:36:ec:a5:f7:
95:fe:7e:3a:c2:73:3a:a2:0b:ed:25:a7:b4:a1:18:20:2c:7f:
ab:75:45:44:8e:40:95:2c:96:66:88:6f:ec:50:5b:07:2e:06:
0d:22:fa:2b:b3:35:93:37:88:5e:5c:32:71:db:40:0e:86:b0:
f6:75:59:4d:f5:4b:79:85:37:3c:43:a3:fa:e8:30:f5:99:ec:
be:12:0f:fb:89:9d:8c:d6:e4:37:dd:57:2c:4c:10:32:df:38:
85:98:df:ab:85:b9:b7:1d:90:a3:e2:9d:31:db:6b:c0:68:06:
64:95:2e:3e:5d:7a:90:42:af:62:94:05:ac:2d:f2:2c:7d:0a:
38:75:d6:1c:cf:77:3d:4a:e1:1c:87:41:f2:87:dd:6b:c1:13:
9a:f8:86:14:7d:c5:74:0a:86:8b:21:5d:4c:5d:17:21:7e:f4:
3b:b7:a0:79:19:0e:2d:b7:36:f1:fa:3e:24:6b:62:87:79:8e:
87:38:94:01
Yes, that’s an annoying Firefox issue but in this case I don’t think so because it worked with the new cert after restarting cockpit with the same Firefox. The bad cert was valid until 1979 so maybe the date was not set correctly at cert creation.
I’m going to check that again…
! (spend hours on this issue 
)