Mikhmon tickets that do not expire: revalidate profiles and choose the right version
Updated on · MonMikroTik team
Your 24-hour tickets still work after a week? Tickets are no longer deleted or blocked at the end of their validity? This problem very often appears after a RouterOS update, or when profiles were created with a Mikhmon version that does not match the router version. The solution: choose the right Mikhmon version, then revalidate the user profiles.
Why tickets no longer expire
With Mikhmon, expiration relies on two scripts installed on the router for each profile (plan):
- the profile's on-login script: at first login, it writes the expiration date into the ticket's comment;
- a scheduler named after the profile: it regularly reads these dates and deletes or blocks expired tickets.
These scripts parse the router's date character by character. But the date format changed with RouterOS 7.10:
| RouterOS version | Date format | Matching Mikhmon version |
|---|---|---|
| RouterOS v6 | oct/25/2026 | Mikhmon V3 |
| RouterOS v7.0 to 7.9 | oct/25/2026 | Mikhmon V3 |
| RouterOS v7.10 and newer | 2026-10-25 | Mikhmon V7 |
If the script expects one format and the router uses another, it no longer recognizes any date: no ticket expires. This is exactly what happens:
- after updating a router from RouterOS 6 or 7.9 to 7.10 or later: the old scripts stay in place, with the old format;
- when profiles were created with Mikhmon V3 on a recent router, or with Mikhmon V7 on an old router;
- when a profile was copied from another router that does not have the same version.
Step 1: find the router's version and date format
- In Mikhmon Online, the router dashboard shows the RouterOS version.
- In Winbox, open New Terminal and type:
The/system resource print /system clock printversionline gives the version, thedateline the format:oct/25/2026(old) or2026-10-25(new).
Step 2: choose the matching Mikhmon version
Set the router's Mikhmon version according to the table above: V3 if the date is in oct/25/2026 format, V7 if it is in 2026-10-25 format.
On the website: open your router list in Mikhmon, click the router's Modifier (Edit) icon, choose Version Mikhmon: Mikhmon V3 or Mikhmon V7, then save.
In the app: Mikhmon tab, open the router, edit it and choose the Version Mikhmon (V3 or V7), then save.
Step 3: revalidate the user profiles
Revalidating a profile means opening it and saving it again, without changing anything. MonMikroTik then reads the router's actual date format and rewrites the profile's expiration scripts (on-login and scheduler) in the right format. Do it for each profile that has an expiration.
The fastest way: revalidate all profiles in one click
- Open the router page on the website, section Revalider les profils (Revalidate profiles).
- Leave the option Convertir aussi la date d'expiration des tickets déjà activés (Also convert the expiration date of already activated tickets) checked (see below).
- Click Revalider tous les profils (Revalidate all profiles) and confirm.
The result shows the detected date format, the revalidated profiles and the number of tickets converted. Only the expiration scripts are rewritten: speeds, pools and other settings do not change. Profiles that have a custom (non-Mikhmon) script are left as they are.
You can also revalidate profiles one by one:
From Mikhmon Online
- Open Mikhmon Online on the router, Hotspot > User Profiles menu.
- Click a profile name to open it.
- Check Expired Mode (for example Remove & Record or Notice & Record) and Validity (for example
1d). A profile set to None never expires: that is intended. - Click Save.
- Repeat for each profile.
From the mobile app
- Mikhmon tab > your router > Dashboard > Profils utilisateur (User profiles).
- Tap a profile, check the expiration mode and validity, then tap Enregistrer (Save). The message Profil mis à jour (Profile updated) confirms it.
- Repeat for each profile.
Check that it is fixed
- Log in with a new ticket: in Hotspot > Users, its comment should show an expiration date in the same format as the router's date.
- In Winbox, System > Scheduler should contain a task named after each profile, enabled, with a recent Last Run date.
- Run a test with a short-validity profile (for example
10m): the ticket should be deleted or blocked shortly after its validity ends.
What about tickets activated before the fix?
Never-used tickets cause no problem: their expiration date will be written in the right format at their first login.
However, tickets already activated before the router update keep a date in the old format in their comment (for example oct/25/2026 14:30:00). The new script does not recognize it, and these tickets will not expire automatically.
With the Revalider tous les profils button, with the conversion option checked, these dates are converted automatically to the new format (oct/25/2026 14:30:00 becomes 2026-10-25 14:30:00): there is nothing else to do.
If you revalidate profiles one by one, convert these tickets by hand:
- in Hotspot > Users, spot the comments in
month/day/yearformat; - if the date has passed, delete or disable the ticket;
- otherwise, rewrite the date in the new format, for example
oct/25/2026 14:30:00becomes2026-10-25 14:30:00, or let it finish and delete it by hand afterwards.
This cleanup only needs to be done once: the following tickets will expire normally.
Other possible causes
| Cause | Solution |
|---|---|
| The profile is in None mode (no expiration) | Choose an expiration mode and a validity, then save. |
| The profile's scheduler was deleted or disabled | Revalidate the profile: the scheduler is recreated. |
| The profile was created or edited in Winbox, without Mikhmon | It does not have the Mikhmon scripts: open it in Mikhmon Online and save. |
| The router's time is wrong (after a power cut) | See Tickets that stop working after a power cut. |
| The ticket's comment was edited by hand | The script no longer recognizes the date: fix the comment or delete the ticket. |
Prevent the problem from coming back
- After every RouterOS update, check the date format and revalidate your profiles.
- Keep the router's Mikhmon version aligned with its RouterOS version.
- Create and edit your profiles from Mikhmon Online or the app, not directly in Winbox.
- For a new router, the configuration generator creates profiles with scripts in the right format.