From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 429 Too Many Request error from IPFire Community
Date: Fri, 17 Mar 2023 12:25:28 +0000 [thread overview]
Message-ID: <52C87D99-E2DF-40B6-83B2-46F00D984C8C@ipfire.org> (raw)
In-Reply-To: <EC92C0A8-4F46-463F-806B-292E38991227@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
Hello everyone,
We are back!
There is some bot that is loading the front page again and again and again… And nginx couldn’t distinguish clients by their IP address because this is hard to configure.
So all fixed. Thanks for letting me know.
Best,
-Michael
> On 17 Mar 2023, at 11:13, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>
> Hello Adolf,
>
> Thanks for the email. I am getting the same error… Will investigate…
>
> -Michael
>
>> On 17 Mar 2023, at 11:12, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Everyone,
>>
>> Just in case you aren't aware, the IPFire community is giving me a 429 Too Many Requests message most of the time.
>>
>> The IPFire Blog, Wiki, Bugzilla, Dev mailing list are all working fine.
>>
>> All menu items on the IPFire Blog are working except for Community.
>>
>> Community was working fine for me before I went for a walk with my dog. When I came back and I opened the IPFire Community on my android phone it said there was a new message in the forum so I clicked on it and that is when it came back with the 429 Too Many Requests message.
>>
>> Looking up the message the info on it said that I was overloading the IPFire Community server and so was being blocked.
>>
>> I don't believe I am sending too many, or if I am then I don't know what changed in the last 1.5 hours.
>>
>> Any suggestions on what my problem might be and how to resolve/stop it?
>>
>> Regards,
>>
>> Adolf.
>>
>> --
>> Sent from my laptop
>>
>
prev parent reply other threads:[~2023-03-17 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 11:12 Adolf Belka
2023-03-17 11:13 ` Michael Tremer
2023-03-17 12:25 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C87D99-E2DF-40B6-83B2-46F00D984C8C@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox