Rhinobase Next
Get the ISO
Rhinobase Next · self-hosted

LAN client setup

Install the right trust settings for desktops and phones on your local network.

One guide for every client device

Connect Windows, Linux, macOS, Android and iPhone/iPad devices to the same Rhinobase Next LAN server. Choose your platform below.

Windows · Linux · macOS · Android · iPhone / iPad · Latest guide changes

Use your server's HTTPS address

Use the HTTPS address shown at the end of server setup. Pressing Enter at the address prompt selects the server's current IP. If you chose a name such as rhinobase.home.arpa, client devices must resolve that name to the server IP. See IP and local DNS for phones.

Get the files from your own server

The server generates client files in /opt/rhinobase/public/lan-client/. Ask the administrator to transfer the appropriate ZIP through authenticated SFTP/WinSCP or another trusted method. Extract the ZIP and keep its files together. Each ZIP contains its own README-LAN-CLIENTS.txt.

DeviceServer-generated package
Windowsrhinobase-windows-client.zip
Linuxrhinobase-linux-client.zip
macOSrhinobase-macos-client.zip
Androidrhinobase-mobile-clients.zip — use local-ca.crt
iPhone / iPadrhinobase-mobile-clients.zip — use rhinobase-local-ca.mobileconfig

The CA belongs to this server installation. Never distribute a .key file or use a certificate from an unknown server. Reinstalling the server may generate a new CA that must be installed on clients again.

After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. Closing a tab is not sufficient. Use this step after certificate setup on every platform.

Windows

  1. Extract rhinobase-windows-client.zip. The required files are Install-RhinobaseClient.bat, Install-RhinobaseClient.ps1, client.json and local-ca.crt. If your server provides these as individual files, copy all four into one folder.
  2. Double-click Install-RhinobaseClient.bat in File Explorer and approve the Windows Administrator prompt. The BAT launches PowerShell itself and verifies the certificate checksum. Its execution-policy bypass applies only to that PowerShell process.
  3. The installer trusts the local CA and can update the hosts mapping when a hostname was chosen. IP-based setup needs no hosts mapping.
  4. After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. Open the exact HTTPS address displayed by the installer.

Linux

  1. Extract rhinobase-linux-client.zip.
  2. Choose Run in Terminal for Install-RhinobaseClient.sh, or open a terminal in the extracted folder and run:
bash Install-RhinobaseClient.sh
  1. Approve the administrator password prompt. The installer supports Debian/Ubuntu and Fedora/RHEL certificate stores. Current packages check that the hostname resolves to the server IP and add a hosts entry if needed.
  2. After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. Open the server's exact HTTPS address. If an unknown issuer warning remains, follow the browser certificate steps.

macOS

  1. Extract rhinobase-macos-client.zip and keep all files together.
  2. Double-click Install-RhinobaseClient.command. If macOS blocks the script, verify that it came from your own server, then use System Settings → Privacy & Security → Open Anyway if shown.
  3. Approve the administrator password prompt. The installer verifies the CA checksum, adds the CA to the System keychain and can add a hosts mapping for a local hostname.
  4. After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. Open the server's exact HTTPS address.

Android

  1. Extract rhinobase-mobile-clients.zip and transfer local-ca.crt to the device.
  2. In device Settings, search for Install a certificate or CA certificate. Choose the CA certificate option and select local-ca.crt.
  3. Approve the device security prompt after confirming the file came from your own server. Menu names vary by manufacturer and Android version; a screen lock may be required.
  4. Join the Wi-Fi network that can reach the server. After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. For the first test, open the server's LAN IP over HTTPS.

Chrome shows ERR_TOO_MANY_RETRIES

  1. Open Android Settings → Apps → Chrome and tap Force stop.
  2. Open Permissions. If Nearby devices or Local network is listed, allow it. If it already shows Allow, switch it to Don't allow and then back to Allow.
  3. Reopen Chrome and retry the same HTTPS IP address. If the error persists, restart the phone once and retry.

If the permission is unavailable or the error continues, try the same HTTPS address in a second browser and report the error code to the server administrator. Android app permission help

iPhone / iPad

  1. Extract rhinobase-mobile-clients.zip and open the rhinobase-local-ca.mobileconfig file from your own server. The profile is generated locally and is unsigned.
  2. Open Settings → Profile Downloaded and tap Install. If needed, look for the profile under General → VPN & Device Management. If the pending profile expires, open the trusted file again and install it promptly.
  3. Go to Settings → General → About → Certificate Trust Settings and enable full trust for Rhinobase Local CA. This additional trust step is required for manually installed root certificates.
  4. After installation, completely close all open browsers, then reopen your browser before accessing Rhinobase Next. On the server's LAN, open the HTTPS IP address or the configured name.

Apple profile installation · Apple certificate trust settings

IP and local DNS for phones

Join the server's LAN or a Wi-Fi network that can reach it. Guest Wi-Fi may isolate devices. The local CA establishes HTTPS trust. DNS maps a hostname to an IP address.

  1. For an IP test, type https://SERVER_IP using the LAN IP recorded during setup. The administrator can find it as RINOBASE_IP in the server's lan-client/client.env. The server certificate includes the setup IP. Reserve it in DHCP to keep it stable.
  2. For hostname access, create a local DNS A record pointing the chosen hostname to the server's reserved IPv4 address. Use the router's local DNS feature or the DNS server that serves the LAN. If Android uses a custom Private DNS provider, try Automatic when testing the local name.

If HTTPS works by IP and the name fails, check which DNS server the phone uses and whether the local record points to the correct IP. Android Private DNS help

Desktop browser certificate warnings

If the browser reports an unknown issuer after a restart, it may need local-ca.crt in its own trust store. Use the file from your own server's client ZIP.

On Linux, you can first test the certificate with curl from the extracted ZIP folder. Substitute your server's exact HTTPS address.

curl -I --noproxy '*' --connect-timeout 5 --max-time 10 \
  --cacert ./local-ca.crt https://rhinobase.home.arpa/

An HTTP status line confirms that curl verified the certificate with that CA and address. If curl reports a certificate error, share the exact message with your server administrator before importing.

Firefox

  1. Enter about:preferences#connectionSecurity in the address bar. If it opens a different section, search Settings for certificates.
  2. Under Certificates, click Manage certificates. Older versions may show View Certificates.
  3. In Certificate Manager, select Authorities, usually the last tab, and click Import.
  4. Open the extracted client ZIP folder. If the file type menu at the bottom right shows PKCS12 Files, select Certificate Files to see local-ca.crt. Select it and click Open. If you only see PKCS12 options or get a certificate backup password prompt, close the picker and start again from Authorities → Import.
  5. Check Trust this CA to identify websites and confirm. Quit Firefox completely, reopen it and enter the server's exact HTTPS address.

Mozilla certificate authority setup

Chrome or Chromium on Linux

  1. Enter chrome://settings/certificates and open Manage certificates if a separate button appears.
  2. Go to Local certificates → Installed by you → Trusted certificates. Click Import and select local-ca.crt. Older Chromium versions may offer the import under Authorities.
  3. Quit the browser completely, reopen it and enter the server's exact HTTPS address.

Chromium certificate management on Linux

Check access and keep the address stable

Confirm that the browser accepts HTTPS, sign in and allow microphone access when using audio recording. Phones and computers must be able to reach the server over the LAN; internet access is not required for local use.

When the server IP changes, update local DNS or desktop hosts mappings. For an IP-based server URL, update the base URL and TLS certificate and regenerate the client files. If a certificate warning remains, verify the HTTPS address and report the exact error code before signing in.

Latest guide changes

— Added Android Chrome local network permission troubleshooting, mobile IP and DNS checks, iPhone and iPad profile and trust steps and desktop browser certificate import instructions. The LAN client README links here for future updates.

Back to Ubuntu installation · All documentation