Files
proxmox/reports/PROXMOX_SSL_CERTIFICATE_FIX_COMPLETE.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
2026-01-06 01:46:25 -08:00

2.4 KiB

Proxmox SSL Certificate Fix - Complete

Date: 2025-01-20
Error: Connection error 596: error:0A000086:SSL routines::certificate verify failed
Status: Fixed


Issue

The Proxmox VE UI showed error:

Connection error 596: error:0A000086:SSL routines::certificate verify failed

Solution Applied

Certificate Regeneration

Regenerated SSL certificates on all Proxmox cluster nodes using:

/usr/sbin/pvecm updatecerts -f
systemctl restart pveproxy pvedaemon

Nodes processed:

  • ml110 (192.168.11.10)
  • r630-01 (192.168.11.11)
  • r630-02 (192.168.11.12)

Fix Script

Script: scripts/fix-proxmox-ssl-certificate-final.sh

This script:

  1. Regenerates certificates using pvecm updatecerts -f
  2. Restarts pveproxy and pvedaemon services
  3. Verifies services are running
  4. Processes all cluster nodes

What pvecm updatecerts -f Does

  • Forces regeneration of cluster SSL certificates
  • Updates certificate chain
  • Regenerates node-specific certificates
  • Updates root CA certificate
  • Syncs certificates across cluster nodes

Next Steps

  1. Clear browser cache and cookies

    • Chrome/Edge: Settings → Privacy → Clear browsing data → Advanced → "Cached images and files"
    • Firefox: Settings → Privacy & Security → Clear Data → "Cached Web Content"
  2. Access Proxmox UI

    • URL: https://<node-ip>:8006
    • Example: https://192.168.11.10:8006
  3. Accept certificate warning (if prompted)

    • First access may show security warning
    • Click "Advanced" → "Proceed to site"
    • Normal for self-signed certificates in Proxmox

Verification

Check if fix worked:

# Check certificate
openssl x509 -in /etc/pve/pve-root-ca.pem -noout -dates

# Check services
systemctl status pveproxy pvedaemon

If Issue Persists

  1. Clear browser SSL state completely
  2. Try accessing via IP address directly (not hostname)
  3. Check system time synchronization:
    date
    # If wrong: ntpdate -s time.nist.gov
    
  4. Verify firewall allows port 8006
  5. Check services are running:
    systemctl status pveproxy pvedaemon
    

Status

Certificates regenerated on all nodes
Services restarted successfully
Fix complete


Last Updated: 2025-01-20
Status: FIXED