Веб-интерфейс кабины возвращается «отключенным» после попытки входа в систему

Он работал нормально, и единственные изменения, которые были внесены до этой проблемы, - это изменение IP-адресов сетевых интерфейсов.

Это «системный журнал», когда я пытаюсь войти в систему как «root».

      Jan 17 07:21:01 server-hostanme systemd[1]: user@0.service: Succeeded.
Jan 17 07:21:01 server-hostanme systemd[1]: Stopped User Manager for UID 0.
Jan 17 07:21:01 server-hostanme systemd[1]: Stopping User Runtime Directory /run/user/0...
Jan 17 07:21:01 server-hostanme systemd[1143761]: run-user-0.mount: Succeeded.
Jan 17 07:21:01 server-hostanme systemd[1]: run-user-0.mount: Succeeded.
Jan 17 07:21:01 server-hostanme systemd[1]: user-runtime-dir@0.service: Succeeded.
Jan 17 07:21:01 server-hostanme systemd[1]: Stopped User Runtime Directory /run/user/0.

Это «системный журнал», когда я пытаюсь войти в систему как «myuser».

      Jan 17 07:50:04 server-hostanme systemd[1]: Started Session 4789 of user myuser.
Jan 17 07:50:19 server-hostanme systemd[1]: session-4789.scope: Succeeded.
Jan 17 07:50:57 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:50:57 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:50:57 server-hostanme cockpit-ws[2414916]: cockpit-ws: Failed to open certificate file /run/cockpit/tls/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855: No such file or directoryJan 17 07:50:58 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:51:34 server-hostanme systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.service: Succeeded.
Jan 17 07:51:34 server-hostanme systemd[1]: cockpit-wsinstance-https@e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.socket: Succeeded.
Jan 17 07:51:34 server-hostanme systemd[1]: Closed Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Jan 17 07:51:42 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:51:42 server-hostanme systemd[1]: Started Cockpit Web Service https instance factory (PID 2414872/UID 108).
Jan 17 07:51:42 server-hostanme systemd[1]: Starting Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Jan 17 07:51:42 server-hostanme systemd[1]: Listening on Socket for Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Jan 17 07:51:42 server-hostanme systemd[1]: Started Cockpit Web Service https instance e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.
Jan 17 07:51:42 server-hostanme systemd[1]: cockpit-wsinstance-https-factory@8-2414872-108.service: Succeeded.
Jan 17 07:51:42 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:51:42 server-hostanme cockpit-ws[2414972]: cockpit-ws: Failed to open certificate file /run/cockpit/tls/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855: No such file or directoryJan 17 07:51:43 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:51:45 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 17 07:51:45 server-hostanme cockpit-tls[2414872]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.

Это «системный журнал», когда я пытаюсь войти в систему как «root» на другом сервере, где Cockpit работает нормально.

      Jan 17 08:04:14 server-hostanme systemd[1]: Created slice User Slice of UID 0.
Jan 17 08:04:14 server-hostanme systemd[1]: Starting User Runtime Directory /run/user/0...
Jan 17 08:04:14 server-hostanme systemd[1]: Finished User Runtime Directory /run/user/0.
Jan 17 08:04:14 server-hostanme systemd[1]: Starting User Manager for UID 0...
Jan 17 08:04:14 server-hostanme systemd[755974]: Queued start job for default target Main User Target.
Jan 17 08:04:14 server-hostanme systemd[755974]: Created slice User Application Slice.
Jan 17 08:04:14 server-hostanme systemd[755974]: Reached target Paths.
Jan 17 08:04:14 server-hostanme systemd[755974]: Reached target Timers.
Jan 17 08:04:14 server-hostanme systemd[755974]: Starting D-Bus User Message Bus Socket.
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on GnuPG network certificate management daemon.
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on debconf communication socket.
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on Podman API Socket.
Jan 17 08:04:14 server-hostanme systemd[755974]: Listening on D-Bus User Message Bus Socket.
Jan 17 08:04:14 server-hostanme systemd[755974]: Reached target Sockets.
Jan 17 08:04:14 server-hostanme systemd[755974]: Reached target Basic System.
Jan 17 08:04:14 server-hostanme systemd[755974]: Reached target Main User Target.
Jan 17 08:04:14 server-hostanme systemd[755974]: Startup finished in 72ms.
Jan 17 08:04:14 server-hostanme systemd[1]: Started User Manager for UID 0.
Jan 17 08:04:14 server-hostanme systemd[1]: Started Session 777 of user root.

Я уже проверил правила брандмауэра, переустановил Cockpit и все зависимости и уже посещал несколько статей с подобными проблемами, но ни одна из них мне не помогла.