Confirm the origin is reachable and safe before WebOptiva fronts it
The origin is the real server WebOptiva fetches your pages from when they are not in cache — the source of truth behind the site you are accelerating. Confirming it early means cache misses, health checks, and previews all read the same server you already know works.
1. Read the origin step#
In Setup → Setup workflow, step 3 Confirm origin (actor You) states the pending action Provide the public origin Weboptiva should use for cache misses. The panel's hint reads Tell Weboptiva where to fetch your site from. Cache misses and health checks go to this origin.
2. Add the origin#
Press Add origin inside the group 2. Add your origin server. The drawer opens for the origin details; provide a full public HTTP or HTTPS URL that serves your site without a CDN already in front of it. Saving closes the drawer and writes the origin into your draft configuration.
3. Prove WebOptiva can reach it#
Press Check DNS records and watch the platform check Origin reachable — it flips from Waiting to Ready once a request to the origin succeeds. If it reports Needs attention, the usual causes are a hostname that does not resolve publicly, a self-signed or mismatched certificate, or a firewall blocking outbound requests from WebOptiva.
4. Manage more than one origin#
A domain can carry several origins with exactly one marked default. Backup origins, priority order, and per-origin health checks live in Setup → Origins; see Manage origins for failover behavior and the health-check controls.
Expected result#
Step 3, Confirm origin, reads Completed, and the platform check stays Ready while the rest of onboarding finishes. Every origin you add — here or later — passes the same safety guard: public HTTP and HTTPS addresses are accepted, while private, local, and reserved addresses are rejected before any request is attempted.