If LobiShell can’t connect to a server at all — the screen shows Connecting… and just sits there, or fails immediately with no useful message — the most common cause on a recent phone is a missing permission, not a network or server problem. This page walks through the checks in order of likelihood.
First: check what’s actually granted
Open Settings → Permissions inside LobiShell. It shows the current state of every permission the app uses and links straight to the right system screen to fix each one — this is faster than hunting through Android’s own settings.
Local Network access (Android 17, most likely cause)
Recent Android versions require an explicit permission before any app can reach devices on your own Wi-Fi/LAN — the same permission a smart-home app needs to find your lights. LobiShell needs it for any connection to a private IP address (the common 192.168.x.x, 10.x.x.x, 172.16–31.x.x ranges) or a .local hostname.
The system should prompt you for this the first time you connect to a LAN server. If you dismissed that prompt, or it never appeared, the connection will silently fail to reach the host every time afterwards.
How to grant it
- Android Settings → Apps → LobiShell → Permissions.
- Look for Nearby devices (that’s the permission group this falls under, even though the setting is really about your local network) — or a permission literally named Local network on newer Android versions.
- Set it to Allow.
No restart needed — reconnect and it takes effect immediately.
This does not apply to servers reached over the public internet, or over a VPN/Tailscale (their address range, 100.64.0.0/10, isn’t treated as local).
A VPN requirement configured on the connection
If the connection has a required VPN set (Connection settings → Require VPN) and that VPN isn’t currently active, LobiShell refuses to connect and tells you so directly in the terminal and in the connection’s own log. Check:
- Is the required VPN app actually connected right now?
- If you only need this rule while off your home network, the connection has a Skip when on the same LAN option — enable it so being home doesn’t require the VPN too.
- If the rule no longer applies, remove it from the connection’s settings.
Background restrictions blocking the attempt
On some manufacturers (Xiaomi, OnePlus, OPPO, and others), an aggressive battery manager can prevent the connection attempt from ever reaching the network, especially right after the app was reopened from the background. See Connections dropping for the full fix — the same three settings apply here.
Still stuck?
- Reproduce the failed connection attempt once.
- Send the log immediately after: Settings → Send Feedback and Logs.
- Mention your phone model, Android version, and whether the server is on your LAN, over a VPN, or on the public internet.