Trusting the local certificate
The first time you open Tesria, your browser may stop you with a warning such as Your connection is not private or This Connection Is Not Private. Nothing is wrong with your server. This page explains why it happens and walks you through making it go away for good, one device at a time.
Why the warning appears
Every time your browser opens a secure web page, the server shows it a certificate: a kind of ID card that proves the server is who it says it is. The browser only accepts ID cards issued by a short list of organizations it already trusts, called certificate authorities. Public websites get their certificates from them.
A Tesria server on your own network cannot get one of those, because those organizations only issue certificates for addresses on the public internet. So Tesria becomes its own certificate authority. The connection is still fully encrypted; your browser just does not recognize who issued the ID card, so it warns you.
The fix is to tell each device, once, that your Tesria server’s certificate authority is to be trusted. After that the warning is gone on that device for good, for every address the server answers on.
Does this apply to you? Only if you open Tesria at a local address, such as wiki-server.local or localhost. If you open it at a real web address, like wiki.example.com, and see a padlock, your server already has a public certificate and you can skip this page.
What trusting it means
A device that trusts a certificate authority believes it about every website, not only Tesria. That is fine while the authority belongs to your server, whose key never leaves it.
On a network you run yourself, such as your home or your own office, trusting it is all there is to do, the same way you accept a server the first time you connect to it with SSH. On a network someone else controls, such as a shared office or a café, someone could answer in your server’s place the first time. There, check the server’s fingerprint first: it is optional, and described below.
Two ways need nothing trusted on each device at all: reaching Tesria through Tailscale, whose addresses have public certificates (see Reaching Tesria from anywhere with Tailscale), or giving it a real domain (see HTTPS and domains).
The fingerprint (optional)
The fingerprint is a long code that only your server’s certificate has: 64 letters and numbers, usually written in pairs, like 4B:1E:09:…. Every way of trusting on this page shows the fingerprint of the certificate it received. To check it before trusting, paste the server’s into the guide, and its commands then trust nothing unless the certificate matches; on a phone you compare it by eye.
If you check, get it from the server itself, not from the network. The certificate reaches a device over a connection nothing protects yet, so the fingerprint has to come by a different way:
On the server, in a terminal, in the Tesria folder:
docker compose logs app | grep -i fingerprint(on Windows,docker compose logs app | Select-String fingerprint). It shows the SHA-256 fingerprint, and the SHA-1 one that Windows’ own certificate window uses.In Tesria, on the server computer: open
https://localhostthere, then Admin, Settings (Admin is in the top bar; in a narrower window or on a phone it is in the ☰ menu at the left of the top bar, and a tab that does not fit is under ••• at the end of the tabs), Certificate. The card shows the fingerprints only on the server computer itself or through Tailscale, where nothing on the network could have changed them.Ask whoever runs your Tesria, by a way you already trust, such as a message you know is from them.
Before you start
Throughout this page, your-server stands for your server’s address: whatever you type into the browser to open Tesria, without https://. For example, if you open Tesria at https://wiki-server.local, then http://your-server/trust means http://wiki-server.local/trust.
A Tesria on ports of its own, such as a second one on the same computer (see Installing with Docker Compose, under A second Tesria on the same computer), has two addresses: you open it at its HTTPS port, such as https://localhost:8443, and its guide and certificate are at its HTTP port, such as http://localhost:8080/trust. Put the HTTP one after http:// on this page, and give it to the scripts, as localhost:8080. The guide fills in both for you.
About three minutes per device.
Optionally, the server’s fingerprint, from above, on a network you do not control.
Permission to change the device’s settings. On a computer that usually means an administrator account.
The device on the same network as the server, the same as when you use Tesria.
The easy way: the Trust This Device guide
Tesria has a guide built in that asks which device you are on, fills your address into the commands, and tells you exactly what to click. There are three ways to open it:
From your profile. Once you are signed in, open your profile (your picture or initials at the top right of any page) and choose Set Up This Device under Trust This Device.
From the sign-in page. Choose Trust This Device under Did your browser warn that this site is not secure?.
By its address. Type
http://your-server/trustinto the browser. Notehttp, nothttps: the guide is served without encryption on purpose, so a device that does not trust the server yet can open it with no warning. This is the easiest way on a phone.
This page is the reference, not the guide. The guide reaches your device over the same unprotected connection as the certificate, so on a network someone else controls, it could have been changed too. If the guide and this page ever differ, follow this page. The guide never shows a fingerprint of its own, and its commands never fetch a script from your server: the Mac and Windows ones are typed lines, and the Linux one fetches Tesria’s script from GitHub.
If http://your-server/trust does not open, your network or security software may block plain http addresses. Open https://your-server/trust instead and click past the warning once, as described under Getting past the warning the first time.
First, open the guide
Open it any of the three ways above. It starts by explaining the warning and what trusting it means, then has four numbered steps and the optional fingerprint check. The steps below have the same numbers, so you can follow along.
Step 1: Which Device Are You On?
The guide guesses your device from your browser. If it guessed wrong, choose the right one. Everything below changes to match.

Step 2: What Address Do You Open Tesria At?
The guide fills in the address you used to reach it. It has to be the address you normally open Tesria at, because that is the address the command will trust. For a Tesria on ports of its own, it includes the HTTPS port, such as localhost:8443, and its commands download the certificate from the HTTP port. If you type a numeric address such as 192.168.1.50, the guide explains how to find your computer’s name instead, since certificates are issued for names.

Optional: check the fingerprint first
Open Optional: Check the Fingerprint First and paste the SHA-256 fingerprint you got from the server (see The fingerprint above). The commands in the next step change to ones that trust nothing unless the certificate matches. Skip it on a network you run yourself.
Step 3: Trust the Certificate
This is the part that does the work, and it differs a little by device. On a phone the guide takes you through the Settings app; see On a phone below.
On a Mac, you copy one line into Terminal. It downloads the certificate from your server, shows its fingerprint, and trusts it; nothing is installed, and it works with no internet. It asks for your password, because adding a trusted certificate changes a setting for the whole computer.
On Linux, the line downloads Tesria’s script from GitHub, which does the same for your distribution. With no internet, use deploy/scripts/trust-ca.sh from the Tesria folder on the server instead.
On Windows, there is no file to download. You copy one line into PowerShell and press Enter. It downloads the certificate, shows its fingerprint, and Windows asks whether to install a certificate from Caddy Local Authority: that is your server, so choose Yes.
If you checked the fingerprint, “does not match” means stop. Nothing was trusted. Check that you copied the fingerprint from this server and typed the right address. If both are right, something on the network is answering in your server’s place: do not trust it, and try again from another network.
Why a line and not a script on Windows? Windows refuses to run script files downloaded from the internet unless you change a security setting, and on a work computer that setting is often locked. A line you paste in yourself is not affected, and it needs no administrator, because it trusts the server for your own Windows account.
Typing your password shows nothing. In Terminal, and in most command windows, the password you type is hidden completely, not even as dots. That is normal: type it and press Return.
Step 4: Check It Worked
Quit your browser completely and open it again. Closing its windows is not always enough, because some browsers keep running in the background: in Chrome or Edge, type chrome://restart or edge://restart into the address bar; in Safari, press ⌘ Q. Then choose Open Tesria Securely at the end of the guide. If Tesria opens with no warning and the address bar shows a padlock, you are done on this device.
Still says “Not secure”? Check that you opened Tesria by its name, such as wiki-server.local, and not a number such as 192.168.1.50. A number never matches the certificate, however it is trusted. The guide’s last step lists the other causes.
Getting past the warning the first time
To sign in and reach your profile before the device trusts the server, you can tell the browser to go ahead this once. It is safe here because it is your own server on your own network. Do not do this for websites you do not recognize.
Browser | What to choose on the warning page |
|---|---|
Chrome, Edge, Brave | Advanced, then Proceed to your-server (unsafe) |
Safari | Show Details, then visit this website, then Visit Website |
Firefox | Advanced…, then Accept the Risk and Continue |
Some browsers offer no way past, for example on a work computer your IT department manages. Use http://your-server/trust instead.
On a phone
On an iPhone, iPad or Android phone there is no script: you install the certificate and trust it in the Settings app, and can compare its fingerprint by eye first. Open http://your-server/trust on the phone and the guide shows the steps for it. On an iPhone or iPad, use Safari; other browsers there cannot install certificates.
iPhone and iPad
In Safari, open
http://your-server/trust, choose iPhone or iPad, and tap Download the Certificate. Tap Allow. It says a configuration profile was downloaded; that is the certificate.Open the Settings app. Tap Profile Downloaded near the top, then Install, enter your passcode, and tap Install twice more.
Optional, if you have the server’s fingerprint: in Settings, General, VPN & Device Management, tap the Caddy Local Authority profile, then More Details and the certificate, and compare SHA-256 with the server’s. If it differs, tap Remove Profile and stop.
Go to Settings, General, About, Certificate Trust Settings (at the very bottom of About), switch on Caddy Local Authority, and tap Continue. Without this step the certificate is installed but not trusted, and the warning stays.
Android
Android trusts a certificate as soon as it is installed.
Open
http://your-server/trust, choose Android, and tap Download the Certificate. It is saved astesria-ca.crt.Open Settings and search for CA certificate. The menus vary between phone makers; it is usually under Security and privacy, More security settings, Encryption and credentials, Install a certificate. Choose CA certificate, then Install anyway, confirm with your screen lock, and pick
tesria-ca.crt.Optional, if you have the server’s fingerprint: in the same Encryption and credentials screen, open Trusted credentials, the User tab, and tap Caddy Local Authority. Compare its SHA-256 fingerprint with the server’s; if it differs, tap Remove straight away.
Doing it by hand
If you would rather not use the guide, or you are setting up many computers, here are Tesria’s scripts. Every release also carries them on GitHub, and tesria-deploy.zip has them in deploy/scripts. Take them from one of those, not from the server: a script fetched over the same unprotected connection as the certificate could have been changed on the way.
trust-ca.sh is for Mac and Linux, and trust-ca.ps1 for Windows. Each needs your server’s address. Given the SHA-256 fingerprint too, it trusts nothing unless the certificate matches; without it, it prints the certificate’s fingerprint and trusts it:
# Mac or Linux, in Terminal
bash ~/Downloads/trust-ca.sh wiki-server.local
# or, checking it first
bash ~/Downloads/trust-ca.sh --fingerprint <fingerprint> wiki-server.local# Windows, in PowerShell
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Downloads\trust-ca.ps1" wiki-server.local
# or, checking it first, add: -Fingerprint <fingerprint>On Windows, -ExecutionPolicy Bypass is what lets the script run: Windows blocks script files by default, with the message running scripts is disabled on this system. This allows the one script, once, and changes no setting. The script trusts the server for everyone who uses the computer, so it asks for an administrator; add -CurrentUser to trust it for your Windows account only. If your employer has locked scripts, use the single line instead, which is what the guide gives you:
$c = "$env:TEMP\tesria-ca.crt"; Invoke-WebRequest -UseBasicParsing -Uri "http://wiki-server.local/ca.crt" -OutFile $c; $x = New-Object Security.Cryptography.X509Certificates.X509Certificate2($c); Write-Host ("SHA-256: " + ([BitConverter]::ToString([Security.Cryptography.SHA256]::Create().ComputeHash($x.RawData)) -replace '-', ':')); Import-Certificate -FilePath $c -CertStoreLocation Cert:\CurrentUser\RootThe guide gives the same line with the check built in once you paste a fingerprint into it.
Either way, the script downloads the certificate from http://your-server/ca.crt, checks it against the fingerprint if you gave one, adds it to the device’s trusted list, and checks that https://your-server now opens without a warning.
Just the certificate
Some tools and devices want the certificate file itself. It is always at http://your-server/ca.crt and downloads as tesria-ca.crt. On a network you do not control, compare its SHA-256 fingerprint with the server’s before trusting it: on a Mac or Linux, openssl x509 -in tesria-ca.crt -noout -fingerprint -sha256.
Firefox
Firefox keeps its own list of trusted certificates, separate from your computer’s, so it needs one more step after the others:
Download the certificate from
http://your-server/ca.crt.In Firefox, open Settings, then Privacy & Security, scroll down to Certificates, and choose View Certificates….
On the Authorities tab, choose Import… and pick
tesria-ca.crt. If you have the server’s fingerprint, choose View first and compare its SHA-256 fingerprint; if it differs, cancel.Tick Trust this CA to identify websites and choose OK.
If the warning comes back
Quit the browser completely and open it again. Browsers remember the old answer until they restart.
Check the address. A device trusts the server, but a browser only stops warning when it reaches it by a name. Opening it by number, such as 192.168.1.50, can still warn.
Was the server reinstalled or moved? If its certificate storage was deleted, for example with
docker compose down -vor a move to a new machine without it, the server made a new certificate authority, with a new fingerprint. Every device needs these steps again. Ordinary restarts and upgrades never do this.
Applies to | Tesria 0.5 and later |
|---|---|
Updated | September 30, 2026 |
Changes | Revised. |