Connecting to the cockpit via Ubuntu involves using appropriate tools and protocols specific to your system setup.
Connecting to the cockpit via Ubuntu involves using appropriate tools and protocols specific to your system setup.
You're running NAS on Ubuntu 20.04 with Cockpit installed. The login issue you're facing appears only when using the web interface with your credentials. The error message indicates a TLS handshake failure during the connection attempt. It seems like the problem might be related to certificate validation or network configuration. Have you checked your server's certificates, firewall rules, or possibly updated the TLS settings? Also, consider reviewing your system logs for more details.
The issue indicates a certificate error, likely requiring HTTPS for Cockpit on the browser. It appears the fix involved using Apache or NGINX with Cerbot, obtaining a certificate, and setting up an HTTPS reverse proxy. Adjusting the cockpit configuration file and restarting the service may enable internal HTTP access but blocks external connections.
Thank you for your response. I had already addressed that issue by adjusting the configuration. Removing the warning allowed me to access the login page smoothly. Following your suggestion, I switched to using HTTP instead of HTTPS. Now, a different outcome appears: I’m no longer receiving the error message that leads to the log. Instead, I stay on the login screen. The browser even suggested saving my credentials. When reviewing the logs, the error message changes to: "cockpit-tls[2159]: cockpit-tls: gnutls_handshake failed: The TLS connection was non-properly terminated."