The Defend-O-Tron’s web pages use HTTPS with a certificate for *.protected.lan. That certificate is signed by the Awesome-O ROOT CA, the certificate authority of Awesome-O Gadgets. Install the Root CA on the computers you manage the device from, and their browsers trust the device’s pages without a “not secure” warning.
The Root CA is the same on every Defend-O-Tron. Like any root certificate, it lets your computer trust every certificate this CA signs, so install it only on the computers you manage the device from.
defend-o-tron-root-ca.crt.The page also shows the certificate’s subject, its validity dates and its SHA-256 fingerprint, with buttons to copy the fingerprint or the certificate itself. Viewers can open this page too.

The first-time setup’s Root CA step offers the same download.
Before you trust the certificate, check that it is the one your device shows. When you open the downloaded file, your system shows the certificate’s details: it is issued to and by Awesome-O ROOT CA, from Awesome-O Gadgets LLC. Its SHA-256 fingerprint must match the one on the device’s Certificates page. If anything is different, do not install the file.
The steps vary with your browser and operating system. If yours look different, check its own documentation.






.crt file onto the System keychain. macOS asks for an administrator password. Enter it.Certificates trusted in the System keychain are used by Safari, Edge, Chrome and most native macOS apps. Firefox can use its own trust store. See the Firefox tab.
The command depends on which family your distribution belongs to.
sudo cp defend-o-tron-root-ca.crt /usr/local/share/ca-certificates/defend-o-tron.crt
sudo update-ca-certificates
update-ca-certificates reports 1 added on first install. Later runs report 0 added because the file is already in place.
sudo cp defend-o-tron-root-ca.crt /etc/pki/ca-trust/source/anchors/
sudo update-ca-trust
sudo trust anchor --store defend-o-tron-root-ca.crt
On any of the above, confirm that the trust update worked:
curl -sS -o /dev/null -w '%{http_code}\n' https://defend-o-tron.protected.lan/login
200, with no certificate error, means the trust is in place. If you still see a TLS error, restart the program you are using (browser, application and so on) so that it reads the new trust store.
Long-running services (containers, systemd units) usually need a restart to pick up new CAs. They read the trust store when they start.
On Linux, Chrome, Chromium and Firefox do not use the system store above. Add the Root CA to them as well: see the Chrome and Edge and Firefox tabs.
Firefox can keep its own certificate trust store, separate from the operating system’s. If you use Firefox to manage the Defend-O-Tron, import the Root CA there too.
.crt file.The Awesome-O ROOT CA now appears in the Authorities list, and Firefox trusts the device’s pages.
On Windows and macOS, Firefox can also use the certificates you installed in the operating system, when the
security.enterprise_roots.enabledpreference istrueinabout:config. Do not rely on it: if Firefox still warns about the device’s pages, import the Root CA as above. On Linux, always import it in Firefox.
On Windows and macOS, Chrome and Edge normally trust the certificates you installed in the operating system (see the Windows and macOS tabs). Some setups, such as browsers managed by an organization, do not. On Linux, Chrome and Chromium keep their own certificate store and never use the system store.
To check, open the device’s web interface in the browser after you install the Root CA, and restart the browser first. If it still shows a certificate warning, import the Root CA into the browser itself:
chrome://settings/certificates (in Edge, edge://settings/privacy, then Manage certificates).defend-o-tron-root-ca.crt as a trusted certificate. On Windows, choose the Trusted Root Certification Authorities store.The names of these menus change between browser versions. If yours look different, look for the browser’s certificate manager in its privacy or security settings.
Chrome and Chromium on Linux keep their certificates in an NSS database. Install the NSS tools (libnss3-tools on Debian and Ubuntu, nss-tools on Fedora and RHEL), close the browser, then run:
DB="$HOME/.local/share/pki/nssdb"
[ -d "$HOME/.pki/nssdb" ] && DB="$HOME/.pki/nssdb"
certutil -d sql:"$DB" -A -t "C,," -n "Awesome-O ROOT CA" -i defend-o-tron-root-ca.crt
C,, trusts the Root CA to identify websites, and nothing else. Chrome 146 and later keep the database in ~/.local/share/pki/nssdb. Older versions used ~/.pki/nssdb, which Chrome still uses if it exists.