Skip to main content
Dynamic serving is what the recommended reverse proxy fetches from. If your domain is still on prerendered delivery, this page is the switch: it keeps the reverse proxy you already run and changes only where it fetches from. Instead of prerendered files in Obvlo’s content CDN, pages are rendered on request behind a cache — so publishing a page makes it live straight away, with no site rebuild. Everything else stays the same: the same URL structure on your domain, the same proxy configuration shape, the same rollback path.
This is the mode we recommend for every site. If you are setting up for the first time, go straight to Reverse proxy — its examples already point at sites.obvlo.com, and on WordPress the plugin does it for you. Read on if you are already serving prerendered files and want to move.
Dynamic serving is enabled per domain by Obvlo. Ask your account contact to switch your domain over — the portal’s Integration tab then generates your proxy configuration against the right origin automatically, and it is the copy you should paste.

​
What changes

Only the origin host and the Host header change. The path after the host is identical, so a switch is two edits in one file and reverses the same way.
The Host header must match the origin you are fetching from. On dynamic serving that is sites.obvlo.com, not content.obvlo.com. Sending the old value is the most common configuration error when switching, and it presents as every page 404ing.

​
Getting your configuration

Take the generated snippet rather than editing your existing one by hand:
  1. Open your site in the Obvlo portal and go to the Integration tab.
  2. Confirm the URL on your domain where the guides live, e.g. https://yourdomain.com/local-guides.
  3. Copy the snippet for your platform — Cloudflare Workers, NGINX, Apache, IIS or Caddy.
  4. Replace your existing proxy configuration with it and reload your proxy.
The generated snippet already names the correct origin, the correct Host header and the correct deployment path for your site. The Reverse proxy guide explains what each directive in it does and covers prerequisites, SSL and troubleshooting — all of which apply unchanged here.

​
Caching and freshness

Pages are served from a cache in front of the renderer, so a repeat visitor gets a cached response rather than a fresh render.
  • Publishing a page clears that page from the cache. Siblings keep their cached copies, so a small edit does not cost a full re-render of your site.
  • A stale copy may be served briefly while a fresh one renders in the background. This is deliberate — it keeps a slow first render off a visitor’s request.
  • If you run your own CDN in front of Obvlo (for example Cloudflare), that cache is yours to purge. Obvlo cannot clear it, so a publish may take up to an hour to appear through it unless you purge as well.

​
Verifying a switch

Check the pages, not the home page — and check more than one.
  1. Load a guide URL on your domain and confirm the content is current.
  2. Publish a small change to that page in the portal and reload. It should appear within seconds.
  3. Load a second guide that you did not change and confirm it still works.
If pages 404 after switching, re-check the Host header first.

​
Rolling back

Point the same two lines back at content.obvlo.com and reload your proxy. Prerendered files are still in place, so there is no data migration and no waiting — this is why the switch is safe to try.