Looking forward to Nethserver 7.9 being released. Was curious what the timeline is to build and test Nethserver 7.9 now that CentOS has finished it’s work?
Was also curious to @giacomo comment on little changes and new defaults. What changes and defaults were you thinking of implementing for Nethserver 7.9?
Not that this is really in scope but I was able to deploy an RP4 on the latest software and everything so far works for me with fail2ban, firewall, VPN, file share and account provider.
I am not a programmer let alone a developer, but I believe it is premature not to install NethGUI in version 7.9.
There are refinements to do in Cockpit before letting NethGUI down.
For one, Cockpit doesn’t seem to be picking up the right information:
Example:
some quick test:
upgrade: seems to work, on basic firewall + nextcloud + proxy + docker (pihole)
I suppose I have to re-read the changes on netdata better, I see the packages installed, but I don’t see the graphics in the proxy … I will study:)
rc1 install:
install unattende and interactive OK, with raid (always in VM) OK
i had some problems with:
openvpn:
Nov 23 10:29:22 ns79rc1a esmith::event[12979]: Action: /etc/e-smith/events/nethserver-openvpn-update/S10nethserver-openvpn-adjust-certs-permissions FAILED: 255 [0.010826]
Nov 23 10:29:28 ns79rc1a esmith::event[12979]: Event: nethserver-openvpn-update FAILED
webproxy:
Nov 23 10:27:09 ns79rc1a esmith::event[4858]: ERROR: Cannot create output file //etc/httpd/admin-conf.d/lightsquid.conf.5212 No such file or directory
Nov 23 10:27:09 ns79rc1a esmith::event[4858]: [WARNING] expansion of /etc/httpd/admin-conf.d/lightsquid.conf failed
Nov 23 10:27:09 ns79rc1a esmith::event[4858]: Action: /etc/e-smith/events/actions/generic_template_expand FAILED: 1 [0.162455]
Nov 23 10:27:09 ns79rc1a esmith::event[4858]: Event: nethserver-lightsquid-update FAILED
can someone try to replicate them? i’ll try to make some more tests in the afternoon
Those should be still there, I will check. If not, this is a regressions.
This is confirmed, we still have a similar bug with ntopng: both app should be changed to be accessible also from port 443 (thanks to @davide_marini for reporting it).