Repository navigation
Access on Your Home Network
The Linux setup wizard asks where you will open Blank Box. These choices control direct inbound connections to the computer running it:
| Choice | Direct access | Address |
|---|---|---|
| 1: This computer | Use a browser on the computer running Blank Box. | http://127.0.0.1:25265 |
| 2: Trusted home network by IP | Use the server or another device on your trusted home network. |
http://SERVER-IP:25265 on the other device. |
| 3: Same network plus blankbox.local | The same access as option 2, with an optional friendly local name. |
http://blankbox.local:25265, or the same IP address. |
Use the port you selected; 25265 is the fresh-install default. Replace SERVER-IP with the server's local address from its network settings or your router's device list. For example, a server at 192.168.1.50 uses http://192.168.1.50:25265. On a phone, 127.0.0.1 means the phone itself, not your server.
Options 2 and 3 still work directly on the server. Option 3 adds a name, not a new access service. None automatically enables outside-home Internet access or disables outgoing Internet connections. A private proxy or VPN you configured separately keeps its own settings and may provide a route to a loopback listener.
Tailscale Serve still reaches Blank Box on your own server. It can forward a private HTTPS address to the app's localhost port; open the Serve address and its selected HTTPS port, which can differ from Blank Box's internal port. The catalog and media stay on your server. Direct Tailscale-IP access instead needs a listener or published port on that interface. See Tailscale Serve for its separate configuration.
First check that Blank Box opens on the server and that it remains running. For option 2 or 3, try the server-IP address from a device on the same trusted network. Check the actual port and current IP. Guest Wi-Fi and network isolation can block another device.
If the IP address works but blankbox.local does not, use the IP address and check the optional Linux discovery packages/helper. .local discovery does not cross every network segment and can conflict with another device using that name. It does not supply HTTPS or outside-home access.
If server-local access works but the IP does not, check the selected access mode and host firewall. The installer does not open router or firewall ports. Outside-home access needs a separately configured private access path; do not forward a router port just to solve a same-network connection problem.
The default Docker setup also publishes only to host loopback; the Linux wizard's numbered choices do not configure Docker. See the exact Networking and Docker guides for your installation.
Use the guides included with your installed version for its exact commands. Windows remains experimental. Report feedback without sharing household data or credentials.