Short answer: if your Android phone is on the same Wi-Fi as the CasaOS server, use the CasaOS web interface or an SMB-capable file manager. If you are away from home, add a private VPN path first, then access the same CasaOS or SMB address through that tunnel. Do not solve remote file access by exposing SMB directly to the public internet.
“I’m running the server on my old laptop. I just want to open the files on the server from Android.” That is the important part of the original problem: the user did not need another file browser inside CasaOS. They needed a safe network path from the phone to the server.
Start by separating local access from remote access
There are two different jobs hiding inside “browse my CasaOS files from Android.”
- Local access: the phone and CasaOS server are already on the same LAN. You only need a way to browse the files.
- Remote access: the phone is on mobile data, hotel Wi-Fi, or another network. You first need to make the home server reachable without publishing its file-sharing ports to the internet.
CasaOS already supports file sharing over SMB; Zima's CasaOS feature notes specifically describe folder sharing via SMB and access to network storage shared by other devices. That means an Android file manager with SMB support can be a reasonable local-LAN client once the share and credentials are configured. The same CasaOS SMB sharing capability is documented in Zima's CasaOS feature overview.
For remote Android access, build the private network path first
A VPN is the cleanest answer when you want the phone to behave as if it were back on the home LAN. WireGuard carries IP traffic through encrypted WireGuard VPN tunnels. The project also provides an official Android client through Google Play and a direct APK under WireGuard for Android.
The practical flow is simple:
- Confirm CasaOS file access works while the phone is at home.
- Create a WireGuard tunnel between the Android phone and the home network, usually through the router or another always-on host.
- Connect the phone to WireGuard while away from home.
- Open the same CasaOS local IP or SMB share you already tested on the LAN.
This order matters. If local access is broken, adding a VPN only adds another variable.
Do not expose SMB port 445 just to make the phone connect
SMB is designed for file sharing, but directly publishing it to the internet is the wrong shortcut. Microsoft recommends blocking inbound TCP 445 for SMB port 445 exposure and using a protected tunnel for remote file access scenarios.
So if your Android file manager asks for a server address, the safe mental model is:
Android phone → private VPN → home LAN → CasaOS / SMB shareNot:
Android phone → public internet → open SMB port 445Which access method should you use?
| Situation | Best starting point | Why |
|---|---|---|
| Phone and CasaOS are on the same Wi-Fi | CasaOS browser UI or SMB-capable Android file manager | No remote tunnel is required. |
| Phone is away from home | WireGuard first, then CasaOS/SMB through the tunnel | Keeps the server on a private network path. |
| You want a mobile-first ZimaOS workflow instead of CasaOS | Zima Client | ZimaOS has a current mobile client designed for remote files and device access. |
If you later move from CasaOS to ZimaOS, Zima Client remote access covers Android and iOS personal-cloud access without requiring you to build the same workflow manually.
A quick troubleshooting checklist
- Test local first: open the CasaOS dashboard from the phone while on home Wi-Fi.
- Verify the file path: make sure the folder is visible in CasaOS and, if using SMB, that the share can be opened from another LAN device.
- Check credentials: remote connectivity does not bypass share permissions.
- Test from mobile data: disconnect Wi-Fi after the VPN is configured. This proves you are actually using the remote path.
- Avoid public SMB exposure: if port 445 is forwarded on the router, remove that forwarding and use the VPN path instead.
An old laptop is perfectly capable of serving this role if storage, networking, and power are reliable. If you later want a smaller always-on x86 home server with native SATA and dual 2.5GbE, ZimaBoard 2 is the relevant hardware option rather than a requirement for the CasaOS workflow above.
FAQ
Can I browse CasaOS files from Android while I am at home?
Yes. If the phone can reach the CasaOS server on the local network, use the CasaOS web interface or an Android file manager that supports the SMB share you configured.
Do I need a special CasaOS Android app?
Not necessarily. The real requirement is access to the server and its files. On the LAN, a browser or SMB client can be enough. Away from home, the missing layer is usually secure remote connectivity.
Can I just port-forward SMB?
Do not expose TCP 445 directly to the internet for this use case. Use a private tunnel such as WireGuard, then access the share as a private-network resource.
Why does the CasaOS file explorer work but my remote phone does not?
Because the file explorer runs after you have already reached CasaOS. A phone on another network still needs a route back to the home server before the file interface or SMB share becomes reachable.
