NethServer Version: 7.9
Module: Cockpit
Hi all,
I made a backup of the main server (SOURCE) using BackupPC from Stephdl.
I did the TAR of that backup (n0).
I restaured on a new updated NethServer-7.9 (DESTINATION.)
I did:
``/sbin/e-smith/restore-config --no-reinstall **--skip-network**
Shutdown DESTINATION and replace SOURCE with the new DESTINATION and started it…
All is OK: the 3 websites ar there, all the users, etc…
I am able to login to the old Server-Manager (980) and see everything and even change some parameters for a test…
When I tried to login to Cockpit, it gave: Internal error in login process
Messages log:
Jul 9 16:07:53 fred systemd: Created slice system-postfix\x2dget\x2dgroup.slice.
Jul 9 16:07:53 fred systemd: Started postfix-get-group server service (127.0.0.1:51602).
Jul 9 16:09:40 fred systemd: Started Session c1 of user root.
Jul 9 16:09:40 fred systemd: Started Session c2 of user root.
Jul 9 16:09:40 fred httpd: [NOTICE] Nethgui\Authorization\User: user `root` authenticated
Jul 9 16:09:40 fred systemd: Started Session c3 of user root.
Jul 9 16:09:57 fred systemd: Starting Cockpit Web Service...
Jul 9 16:09:57 fred remotectl: /usr/bin/chcon: can't apply partial context to unlabeled file ‘/etc/cockpit/ws-certs.d/99-nethserver.cert’
Jul 9 16:09:57 fred remotectl: remotectl: couldn't change SELinux type context 'etc_t' for certificate: /etc/cockpit/ws-certs.d/99-nethserver.cert: Child process exited with code 1
Jul 9 16:09:57 fred systemd: Started Cockpit Web Service.
Jul 9 16:09:57 fred cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/99-nethserver.cert
Jul 9 16:10:20 fred systemd: Started Session c4 of user root.
Jul 9 16:10:33 fred systemd: Started Session c5 of user root.
Jul 9 16:10:33 fred systemd: Started Session c6 of user root.
Jul 9 16:11:13 fred systemd: Started Session c7 of user root.
Jul 9 16:11:13 fred systemd: Started Session c8 of user root.
It looks like the cetificate (or context) for Cockpit has something wrong.
I re-installed Cockpit to no avail.
I manually renew the certificate:
certbot renew --force-renewal
The new Let’s Encrypt is there and I can see it on the Browser.
Same problem when logging to Cockpit.
I tried to use the standard cert as the default to no avail.
I put back the new cert as the default.
According to the Messages log, it looks like the session is started for user root.
The disks are new SSD and are not full.
All suggestions are welcome,
Michel-André