HTTPS inspection
With Website protection on, stillorigin can inspect HTTPS as well as HTTP. The origin agent sends each Website protection domain's existing certificate from the origin server to your sentries, sealed so only your sentries can read it. You stay responsible for the certificate. stillorigin does not issue one.
Until a sentry has that certificate, HTTPS for the domain is passed through unopened to the origin, and Website protection still applies to HTTP. A domain is marked HTTPS inspected only once at least one ready sentry holds the certificate.
The origin agent
Network protection needs nothing installed on the origin server. HTTPS inspection needs the origin agent on that domain's origin server.
The origin agent is one Linux agent for cPanel/WHM, DirectAdmin, Plesk or a generic server, and for Enhance via its API. It finds each Website protection domain's existing certificate on the origin and sends it to the ready sentries of that domain's cluster — sentries that are online, have an approved HTTPS key, and are up to date enough to inspect HTTPS. It also sends a list of the domains it finds on the origin server, so you can add the ones that aren't protected yet.
The origin agent detects cPanel, Plesk and DirectAdmin and sets this origin server's type. Everything else is Generic. New origin servers start as Generic until the agent reports. You can't change the type in the portal.
It checks again every few minutes, and when a certificate is renewed (for example by a Let's Encrypt deploy hook). If the certificate, the list of sentries or a request to check again has changed, it sends an update.
Install it from Origins: open the origin server, then click Get install command.
Installing the origin agent
The command is shown once. It works once, and must be run as root on the origin server within one hour. If this origin server uses Enhance, tick This origin server uses Enhance before you copy the command. See Enhance.
- In the portal, go to Origins and open the origin server.
- Click Get install command.
- Copy the command and run it as root on that server.
The command looks like this (the portal fills in the one-time token):
curl -fsSL https://control.stillorigin.app/downloads/install-agent.sh | sudo bash -s -- YOUR_TOKEN
The same command is used on cPanel/WHM, DirectAdmin, Plesk and generic Linux servers. The agent detects the panel and reads certificates from the usual places, including AutoSSL, Let's Encrypt and other certificates already on the server. On a cPanel server, the installer also installs the cPanel plugin, and later agent updates keep the plugin up to date. You still need to turn Manage protection on in WHM › Feature Manager; it isn't turned on for existing plans automatically.
After you run it, the origin page shows the origin agent's status, the type it set, its version, and when it was last seen. If you have just created the command, you will see Install command created. Waiting for the origin agent to connect. If an enrolled agent has not been seen yet, the page shows Not seen yet.
Only an account owner can create the install command or remove the agent. The origin agent updates itself.
Enhance
The origin agent never detects Enhance on its own. Tick This origin server uses Enhance before you copy the install command. The hint on that tick box reads: The origin agent detects cPanel, Plesk and DirectAdmin and sets this origin server's type. For Enhance, tick this box before you copy the install command.
On Enhance, run the command once for the whole Enhance install, on a server that can reach your Enhance panel. One origin agent can cover more than one Enhance origin server.
- Open one of the Enhance origins, tick This origin server uses Enhance, and click Get install command.
- If you want the same agent to cover other Enhance origin servers, tick them under Also use this agent for these Enhance origin servers.
- The Enhance command includes placeholders. Replace
ENHANCE_API_TOKENwith an Enhance access token with the Super Admin role (Settings › Access tokens),PANEL_HOSTwith your panel's hostname (not a full URL), andORG_IDwith your organisation ID.
curl -fsSL https://control.stillorigin.app/downloads/install-agent.sh | sudo STILLORIGIN_ENHANCE_TOKEN='ENHANCE_API_TOKEN' bash -s -- YOUR_TOKEN --platform enhance --enhance-url https://PANEL_HOST/api --enhance-org ORG_ID
Restrict the access token to the agent server's IP if you can, and give it an expiry you will renew.
Origin agent status
The origin page, and the Origins list, show the origin agent's status:
| What you see | What it means |
|---|---|
| Connected | The origin agent has checked in within the last 15 minutes. |
| Not connected | An origin agent is installed, but it has not checked in for 15 minutes, or it has not been seen yet. |
| Not installed | No origin agent is installed on this origin server. This includes an install command that has not been used yet, and an agent that has been removed. |
It also shows Last seen {when}, or Not seen yet if the origin agent has not reported, and Version {v}.
Not protected yet
When an origin agent is installed for this origin server, the origin page has a Not protected yet section: Domains the origin agent found on this origin server that you haven't added yet. They aren't protected until you add them.
You can search the list. It has a Certificate column (Found or None found) and First found. Found means the origin agent has a currently valid certificate whose names cover the domain. This is not a full Website protection check: a self-signed or untrusted certificate, or one with a bad key or chain, can still fail once you turn Website protection on. Expired certificates and certificates that don't cover the name show None found.
The line Domain list checked {when} is the last time the origin agent checked, including checks that found no change. If the agent has not sent a list yet, you will see The origin agent hasn't sent this origin server's domain list yet. If every domain it found is already added: Every domain the origin agent found on this origin server is added.
You can select domains and click Add to cluster, up to 500 at a time. Choose a cluster and a protection level: Network protection or Website protection (starts in log mode). Nothing is added until you choose. The add is all-or-nothing: if you choose Website protection and you don't have room for every selected domain (unused included Website protection licences plus unassigned Website protection licences), nothing is added. The error reads: You chose Website protection for {n} domains, but you only have room for {spare} more Website protection licences, so nothing was added. Add a licensed sentry, buy Website protection licences, or add fewer domains.
If you try to add more than 500 at once: You can add up to 500 domains at a time. If the cluster was deleted while the page was open: That cluster no longer exists. Refresh the page and try again.
New domains with Website protection start in log mode.
Approving sentry HTTPS keys
Each sentry has its own HTTPS key for receiving your domains' certificates. Approve a key only if you recognise this sentry. Until you approve it, that sentry passes HTTPS through unopened.
On the sentry's page:
| What you see | What it means |
|---|---|
| Waiting for approval | The sentry has sent a key. HTTPS is passed through unopened until this key is approved. An account owner can click Approve key. |
| Approved | The sentry can receive certificates. Your origin agents will send this sentry its certificates within a few minutes. |
| This sentry hasn't sent a key yet. Update it to the latest version. | The sentry is on an older version that does not send a key. |
| This sentry can't inspect HTTPS yet and passes it through unopened. Update it to the latest version. | The sentry is not yet able to inspect HTTPS. Update it, then approve its key if you are asked to. |
The dashboard also alerts you when a sentry's HTTPS key is waiting for your approval.
Domain HTTPS states
On the Domains list, HTTPS inspected and HTTPS passed through show as icons, explained by a Key under the table. On the domain's Protection tab, and under HTTPS on Edit domain, they show as badges.
HTTPS inspected means HTTPS for this domain goes through Website protection, using the certificate from your origin server. The page also shows how many ready sentries have the certificate, for example "2 of 3 sentries have this domain's certificate." Ready sentries are those that can receive it. If some sentries are still waiting for a key to be approved, or cannot inspect HTTPS yet, those lines appear under the badge, using the same wording as in the portal.
HTTPS passed through means HTTPS for this domain is passed through unopened to the origin. Website protection still applies to HTTP. Further lines explain why:
| What you see | What it means |
|---|---|
| Website protection is off for this domain, so HTTPS is passed through unopened to the origin. | Turn Website protection on for the domain if you want HTTPS inspection. This uses a Website protection licence. See Licences. |
| No origin agent is installed on this domain's origin server. | Install the origin agent on that origin. |
| Waiting for the origin agent to send this domain's certificate. | The agent is installed and has not yet sent a certificate. Wait a few minutes, and check that a certificate for this name is installed on the origin. |
| Your sentries haven't received this domain's certificate yet. The origin agent sends it on its next check. | stillorigin has a valid certificate for the domain, but no sentry in its cluster has it yet. Wait a few minutes for the origin agent's next check. |
| No sentry in this domain's cluster is online and able to inspect HTTPS. | stillorigin has a valid certificate, but no sentry in the cluster is online, has an approved HTTPS key and is up to date enough to inspect HTTPS. Check your sentries are online, approve their keys, and update any that are out of date. |
| No sentry is ready to receive this domain's certificate yet. | Approve each sentry's HTTPS key, and update any sentry that cannot inspect HTTPS yet. |
| Certificate expires date · Issued by issuer | The certificate stillorigin is using, and when it expires. |
If the origin is serving a different certificate from the one your sentries are using, you will also see: Your origin server is serving a different certificate from the one your sentries are using. The origin agent will check again. HTTPS stays inspected on sentries that already have the earlier certificate, until the new one is accepted.
When HTTPS is inspected, those requests count under Allowed/hr and Blocked/hr on Domains, exactly like HTTP, and Passthrough HTTPS / hr drops to about zero. Passed-through HTTPS still counts under Passthrough HTTPS / hr. See Domain traffic columns.
HTTPS status
On the Domains list, HTTPS statuses show as icons, explained by a Key under the table. HTTPS inspected and HTTPS passed through only show when Website protection is on. The statuses are decided in this order:
| What you see | What it means |
|---|---|
| HTTPS inspected | Website protection is on, a valid certificate has been accepted, and it has been delivered to a ready sentry with an approved HTTPS key. This stays inspected even if the origin agent later disconnects. |
| Origin agent not connected | There is no origin agent, or it is pending, removed or has not checked in. A domain that is already inspected keeps that status instead. |
| Certificate found | A currently valid covering certificate is stored, or was in the origin agent's list. This is also shown for domains with Website protection that are waiting on a sentry HTTPS key. It is not a promise that HTTPS inspection will succeed: a self-signed or untrusted certificate can still fail. |
| No valid certificate found | The certificate is expired, does not cover the domain, or was not found. |
| No HTTPS icon | The certificate has not been checked yet. |
You can filter the list with All statuses, or by one of these values. In the filter, inspected domains are listed as Inspected. See Domains.
When a domain's certificate needs attention, its row also shows a Certificate issue marker. Click it to open the domain's HTTPS section, where a problem message explains what to fix. The marker also shows when the certificate expires within 21 days and the origin agent hasn't found a newer one. In that case the HTTPS section shows the expiry date. See Certificate expiry.
Problem messages
When the origin agent cannot use a certificate, HTTPS on Edit domain shows one of these messages. The Protection tab shows whether HTTPS is inspected or passed through. The certificate has to be valid now, cover the domain name, use a matching private key, and have a complete chain to a publicly trusted certificate authority. Self-signed certificates cannot be used for HTTPS inspection.
| Message | What to do |
|---|---|
| No sentry is ready to receive this domain's certificate yet. | Approve each sentry's HTTPS key, and update any sentry that cannot inspect HTTPS yet. |
| The certificate chain on the origin server is incomplete or isn't trusted. Check that the full chain is installed. | Install the full chain, including any intermediate certificates. |
| The certificate on the origin server doesn't cover this domain name. | Replace it with a certificate whose names include this domain. |
| The certificate on the origin server has expired. | Renew it on the origin. HTTPS is passed through unopened until the origin agent finds a renewed certificate. |
| The certificate on the origin server isn't valid yet. | Check the certificate's start date, or wait until it becomes valid. |
| The certificate on the origin server is self-signed. HTTPS inspection needs a publicly trusted certificate. | Replace it with a certificate from a public certificate authority, for example Let's Encrypt. |
| The origin agent couldn't find a certificate for this domain on the origin server. | Install a certificate that covers this domain name on the origin, then wait for the origin agent to check again. |
| The origin agent couldn't send this domain's certificate securely. It will try again. | Wait for the origin agent to try again. If the message stays, contact stillorigin support. |
| The origin agent reported a problem reading this domain's certificate. | Check the certificate on the origin, then wait for the origin agent to check again. If it continues, contact stillorigin support. |
| The private key on the origin server doesn't match its certificate. | Install the certificate and the private key that belong together. |
| This domain isn't on an origin server this origin agent is set up for. | Check that the domain's origin in the portal is one the agent is installed for. On Enhance, tick that origin under Also use this agent for these Enhance origin servers, or install the agent on that origin. |
Certificate expiry
You remain responsible for renewing the certificate on the origin server (for example AutoSSL or Let's Encrypt). The origin agent sends the renewed certificate once it finds it.
If no newer certificate has been found, account owners are emailed once when a certificate expires in 21 days, again at 7 days, and again when it has expired. The dashboard also shows an alert.
The subject and note use the domain name and the expiry date. While it is still valid, the subject is "The certificate for {domain} expires in {days} days", and the note is: "The certificate for {domain} expires on {date}, and the origin agent hasn't found a newer one on your origin server. Check that it's renewing (for example AutoSSL or Let's Encrypt)."
After it has expired, the subject is "The certificate for {domain} has expired", and the note is: "The certificate for {domain} expired on {date}. HTTPS for {domain} is passed through unopened to your origin server until the origin agent finds a renewed certificate."
Each email includes the line See the domain's HTTPS status: and a link to the domain's page in the portal.
Removing the origin agent
On the origin's page, an account owner can click Remove agent.
Origin agent removed. HTTPS for this origin's domains with Website protection is passed through unopened until an origin agent is installed again.
To uninstall the software on the server as well, run the install script with --uninstall, as root:
curl -fsSL https://control.stillorigin.app/downloads/install-agent.sh | sudo bash -s -- --uninstall
On a cPanel server, this also removes the cPanel plugin.
Then remove the agent in the portal too, if you have not already.