Skip to main content

What's next and troubleshooting

Your first site is now protected by your sentry, with Network protection, Website protection in blocking, and owner access ready for your customer. Here's what to do next, and where to look when something isn't right.

What's next​

  1. Add your other sites. Add domains by hand on Domains, or in bulk from Not protected yet on each origin's page, up to 500 at a time. See Not protected yet. For a larger move of existing clients, see Migrating existing clients.
  2. Add more origins. Repeat step 3 for each web server. Each licensed sentry includes 2 origins.
  3. Add a second sentry to the same cluster, so your sites stay up if one sentry fails. See Add more sentries.
  4. Lock down SSH on your sentries with the cluster's SSH allow-list.
  5. Close the origin to everyone but your sentries, once DNS points at the sentries, so nobody can go around them. See step 3.
  6. Choose your plan. Before the trial ends, check Billing. To add more sentries, origins or domains with Website protection during the trial, use End trial and upgrade. See Billing and the pricing page.
  7. Invite your team under My account › Users. See Logging in.
  8. Sell Website protection from WHMCS, and add it to cPanel. The free WHMCS module turns Website protection on when an order is set up and gives your clients a Manage protection button. The free cPanel plugin is installed with the origin agent, and gives your cPanel users a Manage protection page for their Website protection sites.
  9. Get to know the portal: Dashboard and activity, Logs and Log reasons explained.

Keeping things running​

  • Updates are automatic. Sentries update in their cluster's update window, and you can update straight away with Force. See Sentry updates. The origin agent updates itself too.
  • Certificates stay your job. Keep AutoSSL or Let's Encrypt renewing on the origin. The origin agent sends renewed certificates to your sentries, and we email account owners before a Website protection domain's certificate expires. See Certificate expiry.
  • Capacity: watch each sentry's Load and Capacity on Clusters. You get an alert email at 80%. See Sentry capacity.
  • Keys: keep your API key and device keys in a password manager. See Your API key.

Troubleshooting​

ProblemWhere to look
The sentry shows OfflineCheck systemctl status stillorigin-sentry and journalctl -u stillorigin-sentry -n 50 on the sentry. It must reach control.stillorigin.app on TCP 443. See Installing a sentry: troubleshooting.
The installer stops with this is not a clean serverThe server has a web server, control panel or something on port 80 or 443. Start from a freshly installed operating system. See Server requirements.
The origin agent shows Not connectedCheck journalctl -u stillorigin-agent -n 50 on the origin. See Origin agent status.
The site shows the stillorigin offline pageThe sentry can't reach the origin. Check the origin's IP address and ports on Origins, and that the origin's firewall and security tools allow every sentry. See step 3.
403 Forbidden for a site you hostCheck the domain is on Domains, in the cluster whose sentries DNS points at. If Website protection is in blocking, check the reason on the domain's Blocks tab or Logs, and Log reasons explained.
HTTPS stops loading after turning on PROXY protocolThe origin and the portal must match. See If HTTPS stops working.
HTTPS inspection stays HTTPS passed throughThe Protection tab, or HTTPS on Edit domain, says why. See Domain HTTPS states.
The origin's logs show the sentry's addressSee step 3 and Trusting the sentry.
You or your visitors are blockedCheck the address at stillorigin.app/check, on Logs › Temporary bans and on Deny list. See Checking an IP address.
Some visitors can reach the site and others can'tWith several sentries in DNS, one may be down. Check each sentry's Status, and remove a failed sentry's A record until it's back.
Traffic figures look wrongConnections and requests count different things. See Domain traffic columns.

Getting help​

Open a ticket from Tickets in the portal. Say which step you're on, and include the sentry or origin name and the output of journalctl -u stillorigin-sentry -n 100 --no-pager (on a sentry) or journalctl -u stillorigin-agent -n 100 --no-pager (on an origin).

Never paste your API key, a device key, an install command or an owner sign-in link into a ticket.