Move Mikhmon from Termux or a Local Computer to a Server
Move the application after saving its configuration and preparing VPN connectivity to the router. Test access, profiles, templates, and reports on the new server before stopping the old installation. Do not reset the router to move the application.
Applies to: Mikhmon V3 ยท Mikhmon Pro
- Category
- Setup
- Read time
- 2 min
- Published
- Updated
- Language
- English
Identify what lives in the application and on the router
HotSpot accounts live on the MikroTik, while session settings, logos, and templates can live in the application installation. Record router locations, connection addresses, application version, and templates.
Keep a private backup of the old installation. Configuration files may contain credentials; do not upload the entire folder to a forum or public link.
Prepare the new server without disrupting the old path
Choose a server that runs the destination application version. If moving from V3 to Pro V5, verify template and settings compatibility rather than assuming they can be copied unchanged.
Connect through VPN remote and use the tunnel address in the new session. Do not expose the API to the internet for easier server access.
Test a workflow before stopping Termux
Open the new address from a phone, find an existing account, create a test voucher, and check printing and required reporting. Verify the router identity and selected profile.
Once results match, update team bookmarks and stop the local server. Keep the old copy for recovery. Avoid modifying profiles or running cleanup from both installations during the move.
If the old server often stops
Check whether the process stops when the screen sleeps, connectivity changes, or the battery runs out. Hosting can reduce dependence on that device, but the router and VPN route must still work.
An Armbian or OpenWrt STB also needs power, storage, network, and application-service checks. Do not assume all local-server failures share one cause.