Skip to content
WebShield Docs

A site without your own server

How to host a landing page, business card site or documentation made of ready files with us and publish it on your domain — without a server of your own.

If a landing page, business card site or documentation made of ready files runs on your own server, that server needs updates, certificate care and headroom for traffic peaks — even though serving files does not require a server of your own.

The fix is to host the files with us. The site is served from cache on nodes close to the visitor, behind the same protection as proxied sites, and the certificate is issued and renewed automatically.

What you get: your site on your domain over HTTPS, updated by uploading a new folder, with no server to look after. You need: a domain and access to your registrar or DNS provider; a ready site — a folder with index.html at its root. Time: half an hour, plus waiting for the nameserver change if you move DNS.

Site Build How to upload Auto-publishing
Business card, a few HTML files not needed drag files into the panel not needed
Landing page depends ZIP archive or CLI optional
Generators, documentation required CLI yes, step 7

Upload the build output, not the sources.

Generator Command Folder Preset Clean URLs
No generator — site folder Plain HTML Directory index
Hugo hugo --minify public/ Hugo Directory index
Astro, Starlight npm run build dist/ Astro Directory index
Docusaurus npm run build build/ Plain HTML Directory index
MkDocs mkdocs build site/ Plain HTML Directory index
VitePress npm run docs:build docs/.vitepress/dist/ Plain HTML HTML extension
Eleventy npx @11ty/eleventy _site/ Plain HTML Directory index
Jekyll bundle exec jekyll build _site/ Jekyll Directory index
Gatsby npm run build public/ Gatsby Directory index
Next.js with output: 'export' npm run build out/ Next.js (export) HTML extension
Vite (React, Vue, Svelte) npm run build dist/ SPA Exact path only

Check the build folder:

  • index.html is at the root, not in a subfolder;
  • there is a 404.html — it’s shown for addresses that don’t exist.

Packed the site inside an outer folder? When uploading in the dashboard, choose Contents at root when asked where the files should go. This works for ZIP archives and for picked or dropped folders containing index.html; see Uploading files.

Pick one option:

  • A. Nameservers at WebShield. The domain’s DNS moves to us. The site works on both www and example.com without manual records. Suits zones not tied to another provider.
  • B. DNS stays with you. Nameservers don’t change; the names you need are connected with records at your current provider. Suits zones hosted in Cloudflare, Route 53 and the like.
  1. Control panel → Domains → Add domain, enter example.com.

  2. Keep record import on and review the list it finds: mail and other service records must be there.

  3. At your registrar, replace the nameservers with these two — no others:

    nsbox.webshield.pro
    nshub.webshield.pro
  4. In Domains, click Check. The status you need is Delegated. It usually takes a couple of hours, but can take up to two days depending on your registrar.

You don’t need to add a record for the site. If the name already has an A or CNAME, publishing switches it to WebShield, and taking the site down brings it back.

The name must not have Proxy enabled: a name works either as a protected server or as a static site.

More in Transfer domain control.

  1. Control panel → Domains → Add domain, enter example.com — the domain itself, without www.

  2. Choose Keep your DNS and add records. The Hosts section opens.

  3. Add a name → www → Host a static site.

  4. At your DNS provider, add the record from the name’s card:

    _acme-challenge.www.example.com. CNAME <address from the card>
  5. Click Check and wait for the certificate — a few minutes.

Apex domains and ALIAS records are covered in Connect without changing nameservers.

  • Option A: Sites → New site → pick a DNS name from the list, or New name… and type, say, www. Names with proxying or an existing site can’t be picked.
  • Option B: the site is created automatically once the name is verified and is already listed under Sites.

A new site has the Draft status and is not visible to visitors.

Open the site with Manage.

  1. Site generator — pick the preset from the table in step 1. It fills in the other fields.
  2. Clean URLs — check against the table. If the value doesn’t match your generator, only the home page opens and every other page returns 404.
    • Directory index — the /about page is stored as about/index.html.
    • HTML extension — the /about page is stored as about.html.
  3. 404 page — 404.html.
  4. SPA mode — only for apps with in-browser routing (React Router, Vue Router). Turn it off for documentation, landing pages and business card sites: otherwise a wrong address returns the home page with status 200, and search engines index duplicates.
  5. Publish over HTTPS — normally on.
  6. Bot protection — leave it off at launch. For documentation and landing pages that need to show up in search, don’t enable Browser check unless you have to.
  7. Click Save settings.

Suits business card sites and landing pages.

  • Files: drag files or a folder into the upload area. They are added to what’s already uploaded; matching paths are replaced.
  • ZIP archive: Upload a ZIP archive → Choose ZIP. The archive fully replaces the existing version.

Zip the contents of the build folder, not the folder itself:

Terminal window
cd public && zip -r ../site.zip . && cd ..

Review the file tree and click Publish.

Suits automation: the CLI uploads only changed files and publishes the site.

Terminal window
curl -fsSL https://raw.githubusercontent.com/webshieldpro/webshield-cli/main/install.sh | sh
webshield auth login
webshield sites publish www.example.com --dir ./dist

Create the login token under Settings in the panel. The --dry-run flag lists the changes without uploading.

If the site is already in WebShield object storage, use the Publish from an S3 bucket block on the site card.

  1. Wait for the Published status.

  2. Check the response:

    Terminal window
    curl -I https://www.example.com/

    Expected: HTTP/2 200. On the first publish the certificate takes a few minutes; if HTTPS doesn’t respond, try again later.

  3. Option B only: if you didn’t move the domain, switch the name — add this record at your DNS provider:

    www.example.com. CNAME <address from the card>

    You’ll get an email once traffic flows through WebShield.

  4. Open inner pages, images, search (for documentation) and any non-existent address in a browser — your 404 page should appear.

If the site is built by a generator and kept in a repository, you never have to upload it by hand: publishing from CI is one CLI command in the pipeline. Step by step for GitHub Actions, GitLab CI, Gitea and Forgejo — in the guide The site updates itself after git push.

Task For Where to set up
Contact or lead form without your own server landing page, business card A contact form without a backend
Redirect old addresses after a move documentation, landing page Redirects
Send some paths to your own server landing page with an API API on the same domain
Traffic and bot share all Statistics
Symptom Cause and fix
The name is missing from the list or can’t be picked Proxy is enabled for the name, or a site already exists.
404 on every page, including the home page index.html is not at the root: the archive was zipped together with its folder.
Home page opens, other pages return 404 Wrong Clean URLs mode. Check how the page is stored in the build folder: about/index.html or about.html.
Styles and scripts don’t load The build uses a base path or a local server address. Check base/baseURL/site_url in your generator’s settings.
A non-existent address opens the home page SPA mode is on. Turn it off for documentation and landing pages.
HTTPS doesn’t work after 30 minutes If the domain has CAA records, add letsencrypt.org. For option A, check that the status is Delegated.
Publishing fails with a line number There’s an error in _redirects — fix the line shown.
Upload rejects .exe, .apk and similar Executable files are available on commercial plans only.

If your case isn’t listed, see Troubleshooting or contact support from the panel.