• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Bad flood reports..

Status
Not open for further replies.
D

dognose

Chevereto Member
I keep getting flood reports, when they shouldn't be triggered.
It's being triggered for an API upload from an ip address I own,
so, I know whats happening from both sides ...

I have it set to 60 per minute, and higher for others.

Here is the report:
Uploads per time period
Minute: 60
Hour: 65
Week: 227
Month: 842

Going through the access log immediately after getting this report:

1 in last minute
13 in last hour
125 today

So, any idea what's going on here?
 
API is under the same flood report as any normal upload. In the future the API will be user based so this won't be an issue.
 
I understand that. The problem is that it's reading 60 uploads in a minute when I know for a fact that it's impossible. Or, am I understanding flood reports wrong?
 
This is the flood query:
Code: 
SELECT
COUNT(IF(image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 MINUTE), 1, NULL)) AS minute,
COUNT(IF(image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 HOUR), 1, NULL)) AS hour,
COUNT(IF(image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 DAY), 1, NULL)) AS day,
COUNT(IF(image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 WEEK), 1, NULL)) AS week,
COUNT(IF(image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 MONTH), 1, NULL)) AS month
FROM chv_images WHERE image_uploader_ip='THE_IP' AND image_date_gmt >= DATE_SUB(NOW(), INTERVAL 1 MONTH)

You should run that query and post the output.
 
Well, I see the problem. Now() is not in GMT time.
For me, there is a multi hour difference.

using utc_timestamp() instead of Now() seems to correct the problem. ..
 
Yes, you are right. To use this in a safer way I will use UTC_TIMESTAMP() instead of NOW().
 
Status
Not open for further replies.
Back
Top