Skip to main content
barisben
barisben
New Member
June 10, 2025
Question

Web Filter Time Quota Keeps Counting Incorrectly After User's First Access

  • June 10, 2025
  • 3 replies
  • 687 views

Hi, We have a web filter profile which is named QA_WF and it has a 3 hours time quota for category 25 (Streaming Media and Downloading) and category 37 (Social Networking). Quota keeps counting incorrectly even though no activity has been performed in this category. Version 7.4.5

 

QA_WF has quota config;

config quota edit 1 set category 25 set duration 3h next edit 2 set category 37 set duration 2h next end

 

In the SS_1.png file, you can see all category 25 logs. The first log was recorded at 2025-04-30 11:05:28 and Quota Used:0. After that, there is no recorded log until 12:13:48 in this category and the user just opened-closed that tab (a Youtube video and Facebook page same for both (not tested Facebook in screenshots but we tested it)) and shutdown the machine. But as you can see in the SS_2.png file, the actual time is shown in the bottom right and the user has 56 minutes left at 13:08.

 

So once this user's quota starts counting, it keeps counting even though no activity is being performed.

 

15736618_Screenshot_1.png

15736619_Screenshot_2.png

3 replies

Jean-Philippe_P
Staff & Editor
Jean-Philippe_P
Staff & Editor
June 13, 2025

Hello barisben, 

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

 

Thanks, 

Jean-Philippe - Fortinet Community Team
Jean-Philippe_P
Staff & Editor
Jean-Philippe_P
Staff & Editor
June 15, 2025

Hello,

 

We are still looking for an answer to your question.

 

We will come back to you ASAP.

 

Thanks,

Jean-Philippe - Fortinet Community Team
Jean-Philippe_P
Staff & Editor
Jean-Philippe_P
Staff & Editor
June 16, 2025

Hello barisben,

 

I found this solution. Can you tell me if it helps, please?

 

The issue you're experiencing with the quota counting incorrectly could be due to several factors. Here are some steps to troubleshoot and potentially resolve the issue:

 

  1. Session Timeout Settings: Check the session timeout settings in your FortiGate configuration. If the session timeout is set too high, it might cause the quota to continue counting even after the user has stopped activity.

  2. Idle Timeout: Ensure that the idle timeout settings are configured correctly. If the idle timeout is not set, the session might remain active, causing the quota to continue counting.

  3. Browser Behavior: Some browsers might keep connections open even after a tab is closed. This can cause the quota to continue counting. Test with different browsers to see if the issue persists.

  4. Check for Background Processes: Ensure there are no background processes or applications that might be accessing the internet and consuming the quota.

  5. FortiOS Version: Since you are using version 7.4.5, consider checking for any known bugs or issues related to quota management in this version. Upgrading to a newer version might resolve the issue if it's a known bug.

  6. Logs and Monitoring: Review the logs and monitor the traffic to see if there are any unexpected activities or patterns that might be causing the quota to count incorrectly.

  7. Configuration Review: Double-check the configuration of the web filter profile and quota settings to ensure they are set up correctly.

 

If the issue persists after these steps, consider reaching out to Fortinet support for further assistance.

Jean-Philippe - Fortinet Community Team
barisben
barisbenAuthor
New Member
June 17, 2025

Hi, thank you for your reply.

 

  1. It is default 3600.
  2. It is 20 minutes.
  3. It was tested but the result is the same.
  4. There are no background processes or applications. Even as it is, it's impossible for background processes to stay active when the computer is shut down.
  5. I checked it but there is no known bug related to this issue.
  6. I checked it but there is nothing.
  7. Completely sure.

I will try to go with support.

Terms & ConditionsAccessibility statement