Not re-enabling the user after Periodic Usage Reset

[Ashaxer]

Describe the bug
When the user reaches its periodic usage limit, marzban will disable user access to the servers.
After Periodic Usage Reset happens, the user's periodic usage will reset to 0 but SOMETIMES marzban does not enable the user access.

To Reproduce
I didn't find any pattern in the bug happening.

Expected behavior
If a user has reached its usage limit, when he tests for connectivity of the servers, he will face an EOF error.
In this scenario, user usage has been reset but still gets the EOF error instantly.
The only fix for this bug is to update the user status by opening the user settings in the Admin panel and clicking on "Edit User"
Edit:
Restarting Core also resolves the issue.

Machine details
OS: [e.g. ubuntu 24]
Marzban version: [5.2] (also happened in 4.9)

[erfjab]

Describe the bug
When the user reaches its periodic usage limit, marzban will disable user access to the servers.
After Periodic Usage Reset happens, the user's periodic usage will reset to 0 but SOMETIMES marzban does not enable the user access.

To Reproduce
I didn't find any pattern in the bug happening.

Expected behavior
If a user has reached its usage limit, when he tests for connectivity of the servers, he will face an EOF error.
In this scenario, user usage has been reset but still gets the EOF error instantly.
The only fix for this bug is to update the user status by opening the user settings in the Admin panel and clicking on "Edit User"

Machine details
OS: [e.g. ubuntu 24]
Marzban version: [5.2] (also happened in 4.9)

Added to Tasks ✅

[Ashaxer]

Hi again, since this issue still happening in version 0.7.0, I'm using this script to restart the core using marzban-api periodically by saving it and using cronjobs:

#!/bin/bash
echo "Requesting access token..."
# Replace address and port if necessary
# Replace ADMIN_USER and PASSWORD with actual values
token_response=$(curl -sk 'https://127.0.0.1:443/api/admin/token' \
  -H 'content-type: application/x-www-form-urlencoded' \
  --data-raw 'grant_type=password&username=ADMIN_USER&password=PASSWORD')

access_token=$(echo "$token_response" | jq -r '.access_token')

if [ -z "$access_token" ] || [ "$access_token" == "null" ]; then
  echo "Failed to retrieve access token. Response:"
  echo "$token_response"
  exit 1
fi

echo "Access token obtained: $access_token"

echo "Restarting Core..."
# Replace address and port if necessary 
restart_response=$(curl -sk 'https://127.0.0.1:443/api/core/restart' \
  -X 'POST' \
  -H "authorization: Bearer $access_token" \
  -H 'content-type: application/json')
echo "Restart response:"
echo "$restart_response"