Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Explain direct HTTPS recovery for refused infrastructure redirects

pulse-triage[bot]f2fb8a18ae4d
diff --git a/docs/TROUBLESHOOTING.md b/docs/TROUBLESHOOTING.md
index c8903393a1..8c6010aacb 100644
--- a/docs/TROUBLESHOOTING.md
+++ b/docs/TROUBLESHOOTING.md
@@ -33,6 +33,9 @@ establish safe recovery.
[agent authentication and reporting evidence](UNIFIED_AGENT.md#agent-lookup-returns-http-401-or-403)
before replacing a token or reinstalling. Installer success is not an accepted
report.
+- **Proxmox or PBS rejects an HTTP → HTTPS redirect:** use the
+ [direct HTTPS recovery](#proxmox-or-pbs-rejects-an-http-to-https-redirect)
+ on the existing connection, without replacing credentials or weakening trust.
- **Proxmox or PBS reports a certificate error:** distinguish
[certificate trust, renewal and saved-pin conflicts](TROUBLESHOOTING.md#proxmox-or-pbs-certificate-validation-failed).
Keep verification enabled; a new certificate or a working browser is not
@@ -309,6 +312,35 @@ recreate the incident. Preserve existing configuration, credentials and logs;
[report the evidence already available](#-getting-help). A later recovery does
not explain the earlier failure, and this guidance is not a runtime fix.
+### Proxmox or PBS rejects an HTTP to HTTPS redirect
+
+The error **infrastructure redirects must stay on the same origin** means a
+request was redirected to a different scheme, hostname or port. HTTP → HTTPS
+changes the origin even when the hostname and port stay the same. A browser
+following that redirect does not establish that Pulse can safely forward its
+API credentials there; this is not an invalid-token or permission error.
+
+For this specific HTTP → HTTPS failure, open the **existing** connection in
+**Settings → Infrastructure → Manage → SSL settings**. If its **Endpoint URL**
+starts with `http://` and the intended endpoint supports HTTPS at that same
+hostname and port, change only the scheme to `https://`. Keep the saved
+credentials, **Verify SSL certificate** and **SSL Fingerprint (optional)**
+unchanged. Do not delete and re-add the connection, rotate tokens, clear pins,
+disable verification or restart Pulse to make the redirect work.
+
+If HTTPS requires a different hostname or port, establish the intended address
+and certificate trust independently before editing; do not copy a redirect's
+destination blindly. If direct HTTPS gives a certificate error, use the
+[certificate guidance](#proxmox-or-pbs-certificate-validation-failed), not HTTP
+fallback or a trust bypass.
+
+Save the correction and check the next ordinary poll for the affected members.
+A successful Test alone does not establish every member's polling recovery;
+see [Test Connection and cluster polling](#test-connection-succeeds-but-cluster-polling-fails).
+If the refusal remains, keep the connection intact and use [Getting Help](#-getting-help)
+with the existing redacted error and running version. Keep literal endpoints,
+credentials and full configuration private; no new diagnostic run is required.
+
### Proxmox or PBS certificate validation failed
A TLS error is not an invalid API token or a missing permission. Keep the
diff --git a/frontend-modern/public/docs/TROUBLESHOOTING.md b/frontend-modern/public/docs/TROUBLESHOOTING.md
index c8903393a1..8c6010aacb 100644
--- a/frontend-modern/public/docs/TROUBLESHOOTING.md
+++ b/frontend-modern/public/docs/TROUBLESHOOTING.md
@@ -33,6 +33,9 @@ establish safe recovery.
[agent authentication and reporting evidence](UNIFIED_AGENT.md#agent-lookup-returns-http-401-or-403)
before replacing a token or reinstalling. Installer success is not an accepted
report.
+- **Proxmox or PBS rejects an HTTP → HTTPS redirect:** use the
+ [direct HTTPS recovery](#proxmox-or-pbs-rejects-an-http-to-https-redirect)
+ on the existing connection, without replacing credentials or weakening trust.
- **Proxmox or PBS reports a certificate error:** distinguish
[certificate trust, renewal and saved-pin conflicts](TROUBLESHOOTING.md#proxmox-or-pbs-certificate-validation-failed).
Keep verification enabled; a new certificate or a working browser is not
@@ -309,6 +312,35 @@ recreate the incident. Preserve existing configuration, credentials and logs;
[report the evidence already available](#-getting-help). A later recovery does
not explain the earlier failure, and this guidance is not a runtime fix.
+### Proxmox or PBS rejects an HTTP to HTTPS redirect
+
+The error **infrastructure redirects must stay on the same origin** means a
+request was redirected to a different scheme, hostname or port. HTTP → HTTPS
+changes the origin even when the hostname and port stay the same. A browser
+following that redirect does not establish that Pulse can safely forward its
+API credentials there; this is not an invalid-token or permission error.
+
+For this specific HTTP → HTTPS failure, open the **existing** connection in
+**Settings → Infrastructure → Manage → SSL settings**. If its **Endpoint URL**
+starts with `http://` and the intended endpoint supports HTTPS at that same
+hostname and port, change only the scheme to `https://`. Keep the saved
+credentials, **Verify SSL certificate** and **SSL Fingerprint (optional)**
+unchanged. Do not delete and re-add the connection, rotate tokens, clear pins,
+disable verification or restart Pulse to make the redirect work.
+
+If HTTPS requires a different hostname or port, establish the intended address
+and certificate trust independently before editing; do not copy a redirect's
+destination blindly. If direct HTTPS gives a certificate error, use the
+[certificate guidance](#proxmox-or-pbs-certificate-validation-failed), not HTTP
+fallback or a trust bypass.
+
+Save the correction and check the next ordinary poll for the affected members.
+A successful Test alone does not establish every member's polling recovery;
+see [Test Connection and cluster polling](#test-connection-succeeds-but-cluster-polling-fails).
+If the refusal remains, keep the connection intact and use [Getting Help](#-getting-help)
+with the existing redacted error and running version. Keep literal endpoints,
+credentials and full configuration private; no new diagnostic run is required.
+
### Proxmox or PBS certificate validation failed
A TLS error is not an invalid API token or a missing permission. Keep the
diff --git a/frontend-modern/src/features/docs/__tests__/proxmoxTlsGuide.test.ts b/frontend-modern/src/features/docs/__tests__/proxmoxTlsGuide.test.ts
index b89427702c..280c6c1cf1 100644
--- a/frontend-modern/src/features/docs/__tests__/proxmoxTlsGuide.test.ts
+++ b/frontend-modern/src/features/docs/__tests__/proxmoxTlsGuide.test.ts
@@ -34,6 +34,45 @@ const prose = (element: HTMLElement): string =>
(element.textContent ?? '').replace(/\s+/g, ' ').trim();
describe('Proxmox TLS troubleshooting guide', () => {
+ it('routes a refused HTTP upgrade to direct HTTPS without replacing saved identity or trust', () => {
+ const article = guide('TROUBLESHOOTING');
+ const heading = article.querySelector('#proxmox-or-pbs-rejects-an-http-to-https-redirect');
+ expect(heading?.tagName).toBe('H3');
+ const section = document.createElement('section');
+ for (let next = heading!.nextElementSibling; next; next = next.nextElementSibling) {
+ if (/^H[1-3]$/.test(next.tagName)) break;
+ section.appendChild(next.cloneNode(true));
+ }
+ const text = prose(section);
+ expect(text).toContain('infrastructure redirects must stay on the same origin');
+ expect(text).toContain('HTTP → HTTPS changes the origin');
+ expect(text).toContain('the intended endpoint supports HTTPS at that same hostname and port');
+ expect(text).toContain('change only the scheme to https://');
+ expect(text).toContain(
+ 'Keep the saved credentials, Verify SSL certificate and SSL Fingerprint (optional) unchanged',
+ );
+ expect(text).toContain('Do not delete and re-add the connection, rotate tokens, clear pins');
+ expect(text).toContain("do not copy a redirect's destination blindly");
+ expect(text).toContain('check the next ordinary poll for the affected members');
+ expect(text).toContain(
+ "A successful Test alone does not establish every member's polling recovery",
+ );
+ expect(text).toContain('Keep literal endpoints, credentials and full configuration private');
+ expect(section.querySelector('pre')).toBeNull();
+ for (const id of [
+ 'proxmox-or-pbs-certificate-validation-failed',
+ 'test-connection-succeeds-but-cluster-polling-fails',
+ '-getting-help',
+ ]) {
+ expect(section.querySelector(`a[href="#${id}"]`), id).not.toBeNull();
+ expect(article.querySelector(`[id="${id}"]`), id).not.toBeNull();
+ }
+ const entry = article.querySelector(
+ 'a[href="#proxmox-or-pbs-rejects-an-http-to-https-redirect"]',
+ );
+ expect(entry?.textContent).toBe('direct HTTPS recovery');
+ });
+
it('distinguishes the primary connection test from saved-member polling and agent reports', () => {
const { section } = testScopeSection();
const text = prose(section);