Mikhmon Vouchers Expire Immediately? Check Clock, NTP, and Profile
Check the router date, time zone, and NTP synchronization, then compare profile rules with the voucher login time. An incorrect clock can disrupt expiry scripts, but it is not the only reason an account is rejected.
Applies to: Mikhmon V3 · Pro V5 · NTP example: RouterOS 7
- Category
- Troubleshooting
- Read time
- 2 min
- Published
- Updated
- Language
- English
Inspect time and the account first
After a power outage, compare the router clock with local time. Also check whether the account exists, is disabled, or has exhausted uptime or data limits.
Replace VOUCHER_NAME below. These commands inspect state without deleting users or changing scripts.
/system clock print
/ip hotspot user print detail where name="VOUCHER_NAME"
/log print where topics~"hotspot"RouterOS 7: enable synchronization with your chosen source
In System > NTP Client, inspect existing servers before adding another. This example uses pool.ntp.org and requires working DNS and connectivity. Run the add line only if that server is not already listed.
Wait for synchronized status. Set the location’s time zone under System > Clock; changing the zone alone does not fix an unsynchronized time source.
/system ntp client set enabled=yes
/system ntp client servers add address=pool.ntp.org
/system ntp client print
/system ntp client servers printRouterOS 6 and accounts already removed
RouterOS 6 may have SNTP Client or NTP Client depending on installed packages. Follow that version’s server fields rather than pasting RouterOS 7 server-list commands blindly.
After correcting time, test a new voucher with the same profile. Accounts deleted by scripts do not reappear when NTP is fixed. Inspect backups and sales records before issuing replacements.