d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
2a1b2c63117d95a725c86d5c87732ebe26d1ea2f
proxmox/reports/R630_02_SSL_596_BROWSER_FIX.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Details
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates 
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

6.7 KiB
Raw Blame History

r630-02 SSL Error 596 - Browser Cache Fix (REQUIRED)

Date: 2026-01-06
Error: error:0A000086:SSL routines::certificate verify failed (596)
Node: r630-02 (192.168.11.12)
Status: ⚠️ BROWSER CACHE MUST BE CLEARED

⚠️ CRITICAL: This is a Browser Cache Issue

The SSL error 596 is appearing in the browser GUI because your browser has cached old certificate information. The server-side certificates have been fixed, but the browser needs to clear its cache.

Server-Side Status: ✅ FIXED

What was done on the server:

  • ✅ SSL certificates regenerated on r630-02
  • ✅ SSL certificates regenerated on all cluster nodes (ml110, r630-01, r630-02)
  • ✅ Proxmox services restarted
  • ✅ Certificate chain verified: ✅ OK
  • ✅ Web interface responding: ✅ HTTP 200

Server certificates are valid and working correctly.

Browser-Side Fix: CLEAR CACHE (REQUIRED)

You MUST clear your browser cache and cookies to resolve the SSL error 596.

Method 1: Clear All Browsing Data (Recommended)

Chrome/Edge:

  1. Press Ctrl+Shift+Delete (Windows/Linux) or Cmd+Shift+Delete (Mac)
  2. In the dialog:
    • ✅ Check "Cached images and files"
    • ✅ Check "Cookies and other site data"
    • Time range: "All time" or "Last 24 hours"
  3. Click "Clear data"
  4. Close and completely restart the browser
  5. Navigate to: https://192.168.11.12:8006

Firefox:

  1. Press Ctrl+Shift+Delete (Windows/Linux) or Cmd+Shift+Delete (Mac)
  2. In the dialog:
    • ✅ Check "Cached Web Content"
    • ✅ Check "Cookies"
    • Time range: "Everything" or "Last 24 hours"
  3. Click "Clear Now"
  4. Close and completely restart the browser
  5. Navigate to: https://192.168.11.12:8006

Method 2: Use Incognito/Private Mode (Quick Test)

  1. Open browser in Incognito/Private mode:

    • Chrome: Ctrl+Shift+N (Windows/Linux) or Cmd+Shift+N (Mac)
    • Firefox: Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)
    • Edge: Ctrl+Shift+N (Windows/Linux) or Cmd+Shift+N (Mac)

  2. Navigate to: https://192.168.11.12:8006

  3. If it works in incognito mode, the issue is definitely browser cache

Method 3: Clear Site-Specific Data

Chrome/Edge:

  1. Click the lock icon in the address bar
  2. Click "Site settings"
  3. Click "Clear data"
  4. Check "Cookies" and "Cached images and files"
  5. Click "Clear"
  6. Refresh the page

Firefox:

  1. Click the lock icon in the address bar
  2. Click "Clear Cookies and Site Data"
  3. Refresh the page

Method 4: Reset SSL State (Advanced)

Chrome:

  1. Go to: chrome://settings/clearBrowserData
  2. Advanced tab
  3. Select "Cached images and files"
  4. Select "Cookies and other site data"
  5. Click "Clear data"

Firefox:

  1. Go to: about:preferences#privacy
  2. Scroll to "Cookies and Site Data"
  3. Click "Clear Data"
  4. Check "Cached Web Content" and "Cookies and Site Data"
  5. Click "Clear"

Step-by-Step Fix Process

Step 1: Clear Browser Cache

Follow Method 1 above to clear all browsing data.

Step 2: Close Browser Completely

  • Close all browser windows
  • Make sure browser process is completely closed (check Task Manager/Activity Monitor)

Step 3: Restart Browser

  • Open browser fresh
  • Do NOT restore previous session

Step 4: Access Proxmox UI

  • Navigate to: https://192.168.11.12:8006
  • Use IP address directly (not hostname)

Step 5: Accept Certificate Warning (First Time)

  • If you see a security warning, click "Advanced" or "Show Details"
  • Click "Proceed to 192.168.11.12 (unsafe)" or "Accept the Risk and Continue"
  • This is normal for self-signed certificates in Proxmox

Step 6: Verify No Error 596

  • The GUI should load without SSL error 596
  • You should see the Proxmox login page

If Error Still Persists

Check 1: Try Different Browser

  • Use a browser you haven't used to access Proxmox before
  • Or use a completely different browser (Chrome vs Firefox vs Edge)

Check 2: Check Browser Console

  1. Open Developer Tools: Press F12
  2. Go to Console tab
  3. Look for SSL/certificate errors
  4. Go to Network tab
  5. Refresh page
  6. Check for failed requests with SSL errors

Check 3: Disable Browser Extensions

  • Some security extensions block self-signed certificates
  • Try disabling extensions temporarily
  • Especially: HTTPS Everywhere, Privacy Badger, uBlock Origin

Check 4: Check System Time

  • Ensure your computer's system time is correct
  • SSL certificates are time-sensitive
  • Time mismatch can cause certificate verification failures

Check 5: Check for Proxy/VPN

  • Corporate proxy or VPN may be intercepting SSL
  • Try accessing from a different network
  • Or disable proxy/VPN temporarily

Check 6: Manual Certificate Import (Advanced)

If nothing else works, manually import the root CA certificate:

# Get the root CA certificate
ssh root@192.168.11.12 "cat /etc/pve/pve-root-ca.pem" > pve-root-ca.pem

Chrome/Edge:

  1. Settings → Privacy and security → Security
  2. Manage certificates → Authorities tab
  3. Import → Select pve-root-ca.pem
  4. Check "Trust this certificate for identifying websites"
  5. OK

Firefox:

  1. Settings → Privacy & Security
  2. Certificates → View Certificates
  3. Authorities tab → Import
  4. Select pve-root-ca.pem
  5. Check "Trust this CA to identify websites"
  6. OK

Verification

After clearing cache, verify the fix:

  1. Access Proxmox UI: https://192.168.11.12:8006
  2. Check for Error 596: Should NOT appear
  3. Login: Should be able to login normally
  4. Check Browser Console: No SSL errors

Why This Happens

The SSL error 596 persists in the browser because:

  1. Browser SSL Cache: Browsers cache SSL certificate information for performance
  2. Certificate Change: When certificates are regenerated, browser still has old certificate cached
  3. Security Feature: Browsers cache certificates to prevent man-in-the-middle attacks
  4. Cache Persistence: Cache persists even after server-side fixes

Solution: Clear browser cache to force browser to fetch new certificate information.

Quick Reference

Server Status: ✅ Fixed (certificates regenerated, services restarted)
Browser Action: ⚠️ REQUIRED - Clear cache and cookies
Access URL: https://192.168.11.12:8006
Expected Result: No error 596, Proxmox login page loads

Summary

✅ Server-side: All fixes applied, certificates valid
⚠️ Browser-side: YOU MUST CLEAR BROWSER CACHE
📋 Next Step: Clear browser cache using Method 1 above, then access Proxmox UI

Last Updated: 2026-01-06
Status: ⚠️ AWAITING BROWSER CACHE CLEAR
Critical: The error will persist until browser cache is cleared

Reference in New Issue View Git Blame Copy Permalink