VITEC SSR — Control & Protocol

Status

SSR delivery
ON pages are served from the VPS OFF SPA as before, TYPO3 serves the shell
Toggle: Site Management › Settings › VITEC › SSR delivery. Switching on purges the node cache once.
SSR server
running {health.responseMs} ms
Release {health.release.release} commit {health.release.commit}
Cache: {health.cachedPages} pages · {health.cacheMB} MB of {cacheLimitMb} MB
 not reachable {healthError}
After {failoverAfter} failed checks in a row the cron switches delivery back to the SPA.
Cache warming
0 %
running {health.warming.done} of {health.warming.queued} pages rendered ({health.warming.skipped} still fresh, {health.warming.failed} failed)
Live — updates every 2 seconds.
 Last run: {health.warming.done} of {health.warming.queued} pages rendered ({health.warming.skipped} still fresh, {health.warming.failed} failed 0 failed ) aborted by restart no run since the server started
Health check
ok down {lastSampleAge} ago · {lastSample.response_ms} ms · {lastSample.cached_pages} pages
Every 5 minutes via cron vitec:ssr-health; alert mail and automatic fallback to the SPA after repeated failures.
 no samples yet
Purge webhook
configured endpoint and secret from var/vitec-ssr-purge.env not configured var/vitec-ssr-purge.env is missing or incomplete

Actions

Purge paths

One path per line, e.g. /products/aligo. Drops those pages (all host and query variants) from the SSR cache; they are rendered again on their next request.

Purge everything

For menu or footer changes while auto-purge is off, and after a frontend deploy.

Warm cache

Pre-renders every sitemap page so no visitor waits for a first render. Use it after “Purge everything” or a deploy; progress shows in the status card.

Purge protocol

30 100 500
Time Trigger Paths Result Duration
@{row.crdate} {row.trigger_label} {row.trigger_who} all (*) {row.paths_count} paths {p}
show all {row.paths_count} {p}
ok HTTP {row.http_code} {row.message} {row.duration_ms} ms
No purges logged yet.

Client errors last 24 h — {clientErrorCount24h} reports, newest 50 shown

Browser-side failures reported by the React frontend via POST /api/vitec/client-error (JS errors, unhandled promise rejections, element error boundaries and “chunk reload” after a deploy). Limited to 30 reports per minute and IP, 8 KB per report; IPs are stored anonymized; kept for 30 days (cron vitec:client-error-cleanup). A release older than the one running above means an open tab with an old bundle.

TimeReleaseMessagePageBrowserIP
@{row.crdate} {row.release}— chunk reload error {row.message}
details
Reported@{row.crdate} (entry #{row.uid})
Release{row.release}not transmitted
URL{row.url}not transmitted
Message{row.message}
Stack 
{row.stack}
 no stack transmitted
Browser{row.user_agent}not transmitted
IP{row.ip} (anonymized)
 {row.path} {row.ua_short} {row.ip}
No client errors reported in the last 24 hours.

Health samples last 10 — cron vitec:ssr-health, every 5 minutes

TimeStatusReleaseCacheResponse time
@{row.crdate} ok down {row.release_id} {row.cached_pages} pages · {row.cache_mb} MB {row.response_ms} ms
No samples yet.