Tesria
Tesria.com

Real visitor addresses with Docker Desktop

Tesria notes the network address of every visit: for sign-in limits, security alerts, the audit log, and blocking an address that attacks it. On a Linux server that just works. With Docker Desktop on a Mac or on Windows it does not: Docker Desktop receives every connection itself and passes it on from one address of its own, 192.168.65.1. Your laptop, your phone and a stranger then all look like the same visitor.

Tesria notices this. An alert about that address says every device shares it, and it cannot be blocked, since blocking it would lock everyone out. This page fixes it properly: a small program on the computer itself, where the real address can still be seen, hands each visit to Tesria with its real address attached.

Who needs this. Only Tesria running under Docker Desktop, on a Mac or Windows. On a Linux server, and for visits through Tailscale, there is nothing to do.

Before you start

  • Node.js on the computer Tesria runs on, from nodejs.org. Nothing else is installed.

  • Tesria running as Installing with Docker Compose describes. The script adds its line to the .env file in the Tesria folder, and makes that file if there is none.

On a Mac

Step 1: Run the setup

In Terminal, in the Tesria folder:

Bash / Shell
deploy/docker-desktop/install-macos.sh

It adds one line to .env, moves Tesria’s web server to ports only this Mac can reach, and adds a login item that takes over ports 80 and 443. It ends by saying Tesria answers.

Step 2: Allow incoming connections

If macOS asks whether node may accept incoming network connections, choose Allow. Without it, other devices cannot reach Tesria.

On Windows

Step 1: Open PowerShell as administrator

Open the Start menu, type PowerShell, and choose Run as administrator. Administrator rights are needed to add the firewall rule and the task that starts it when you sign in.

Step 2: Run the setup

Go to the Tesria folder, then run:

powershell
powershell -ExecutionPolicy Bypass -File deploy\docker-desktop\install-windows.ps1

It does the same as on a Mac, with a Windows Firewall rule, and a Task Scheduler task that runs in the background from startup, with no window.

Two Tesrias on one PC? Run the setup in each one’s folder. Each gets its own task, firewall rule and ports, and undoing it in one folder leaves the other alone. The second Tesria’s ports must be set with TESRIA_HTTP_PORT and TESRIA_HTTPS_PORT in its .env, as Installing with Docker Compose describes under A second Tesria on the same computer: the setup reads them from there. If something is in the way, it says so and changes nothing. On a Mac, the setup handles one Tesria per computer.

Check it

Sign in to Tesria from another device, such as your phone on the same Wi-Fi. Then open Admin, Audit (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): the sign-in shows that device’s own address, such as 192.168.1.50, instead of 192.168.65.1.

Worth knowing

  • It runs while you are signed in to the Mac. The Mac’s login item starts when you sign in. On Windows the task starts with the computer, but Docker Desktop itself waits for someone to sign in, so Tesria answers once they have either way.

  • Nothing else changes. Devices keep the same address for Tesria, and the certificate stays the same, so nothing needs trusting again.

  • It cannot be used to fake an address. Tesria’s web server now accepts connections only from this computer, and believes the attached address only from there.

Undo it

On a Mac:

Bash / Shell
deploy/docker-desktop/install-macos.sh --uninstall

On Windows, in PowerShell as administrator:

powershell
powershell -ExecutionPolicy Bypass -File deploy\docker-desktop\install-windows.ps1 -Uninstall

Either puts everything back as it was.


Applies to

Tesria 0.6 and later

Updated

September 30, 2026

Changes

Revised.