Rhinobase Next · self-hosted

Connect Windows clients

Trust this server’s local HTTPS certificate and connect over your LAN.

Use the files from your own server

Every installation creates its own local certificate authority. Copy all three files from /opt/rhinobase/public/lan-client/ into one folder on each Windows client:

  • Install-RhinobaseClient.ps1
  • client.json
  • local-ca.crt

Open Windows PowerShell as Administrator and run the script from that folder:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\Install-RhinobaseClient.ps1

The script checks the certificate checksum and imports the local CA. When a hostname was chosen, it also updates the Windows hosts entry. With IP-based setup it imports the CA without a hosts mapping.

Open the HTTPS address

Restart Chrome and open the address printed by setup: https://rhinobase.home.arpa or https://SERVER_IP. A trusted HTTPS connection is needed for browser microphone recording. Audio-file upload and local transcription also work without internet.

Keep the address stable

A DHCP reservation for the server avoids address changes. With a DNS hostname, update its client mapping if the IP changes. With IP-based setup, a new IP also requires updating the server's base URL and TLS certificate. Rerunning the Windows script alone does not reconfigure the server certificate.