SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Cockpit Authentication Failed After Installation #64

New Issue
Closed
opened 2025-11-20 04:43:11 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:43:11 -05:00
Owner
Copy Link

Originally created by @bannert1337 on GitHub (Nov 17, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When attempting to log in to Cockpit after installation using the Proxmox VE script, authentication fails and returns to the login screen. The console shows a 401 Authentication Failed error.

Environment:

  • Proxmox VE 8.2.8
  • Debian 12 Bookworm
  • Cockpit version: 287.1-0+deb12u3
  • Browser: Floorp Version 11.20.0 (64-bit) | Firefox: 128.5.0

Steps to reproduce:

  1. Install Cockpit using the Proxmox VE script
  2. Navigate to https://[IP]:9090
  3. Enter root credentials
  4. Login attempt fails and returns to login screen

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

Error message from browser console:

cockpit-certificate-ensure[3927]: /usr/lib/cockpit/cockpit-certificate-helper: line 25: sscg: command not found
cockpit-tls[3933]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.

Please provide detailed steps to reproduce the issue.

journalctl -u cockpit shows:
cockpit-tls[3933]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.

Originally created by @bannert1337 on GitHub (Nov 17, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When attempting to log in to Cockpit after installation using the Proxmox VE script, authentication fails and returns to the login screen. The console shows a 401 Authentication Failed error. Environment: - Proxmox VE 8.2.8 - Debian 12 Bookworm - Cockpit version: 287.1-0+deb12u3 - Browser: Floorp Version 11.20.0 (64-bit) | Firefox: 128.5.0 Steps to reproduce: 1. Install Cockpit using the Proxmox VE script 2. Navigate to https://[IP]:9090 3. Enter root credentials 4. Login attempt fails and returns to login screen ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. Error message from browser console: ``` cockpit-certificate-ensure[3927]: /usr/lib/cockpit/cockpit-certificate-helper: line 25: sscg: command not found cockpit-tls[3933]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received. ``` ### Please provide detailed steps to reproduce the issue. journalctl -u cockpit shows: cockpit-tls[3933]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
saavagebueno added the not a script issue label 2025-11-20 04:43:11 -05:00
saavagebueno commented 2025-11-20 04:43:12 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 17, 2024):

Works fine here, did you set a root password?
image
image

@havardthom commented on GitHub (Nov 17, 2024): Works fine here, did you set a root password? ![image](https://github.com/user-attachments/assets/7ee08d6d-7ef8-4860-9608-9118ba154a0a) ![image](https://github.com/user-attachments/assets/a6d55ecc-69e6-4f46-86a7-919ab6b4cb14)
saavagebueno commented 2025-11-20 04:43:12 -05:00
Author
Owner
Copy Link

@bannert1337 commented on GitHub (Nov 17, 2024):

I tried both using the script with Advanced and setting a root password and also the default with root password set after creation. None did work. I also tried privileged and unprivileged LXC.

@bannert1337 commented on GitHub (Nov 17, 2024): I tried both using the script with Advanced and setting a root password and also the default with root password set after creation. None did work. I also tried privileged and unprivileged LXC.
saavagebueno commented 2025-11-20 04:43:12 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 17, 2024):

Maybe a DNS problem? Tested both default and advanced here also, no problem

@havardthom commented on GitHub (Nov 17, 2024): Maybe a DNS problem? Tested both default and advanced here also, no problem
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#64
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?