You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mikrotik by default, works on UTC 00:00 but if you live on another UTC, lets say UTC - 05:00 as example, when you have a user profile that expires in 1 day, then the users of that user profile that try to login for the first time between 19:00:00 and 23:59:59 will be marked as expired as soon as they logged in because when you run your script on login for that user profile, you ask for the next-run of the scheduler with 1d of delay created before, but mikrotik in this case will give only the time, instead of date and time by error, because to them it's the same date since they use UTC 00:00
Mikrotik by default, works on UTC 00:00 but if you live on another UTC, lets say UTC - 05:00 as example, when you have a user profile that expires in 1 day, then the users of that user profile that try to login for the first time between 19:00:00 and 23:59:59 will be marked as expired as soon as they logged in because when you run your script on login for that user profile, you ask for the next-run of the scheduler with 1d of delay created before, but mikrotik in this case will give only the time, instead of date and time by error, because to them it's the same date since they use UTC 00:00
On the example getexp will take 8 as value by mikrotik error and then you choose the current date as the expiration date:
When the scheduler for that user profile is triggered it marks the user as expired exactly at the same time of their first connection.
The text was updated successfully, but these errors were encountered: