public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Charles Brown <cab_77573@yahoo.com>
To: development@lists.ipfire.org
Subject: Re: GIT has had enough and is no longer interested. Thats it!
Date: Mon, 29 Dec 2025 12:23:55 -0600	[thread overview]
Message-ID: <05288ccc-a274-4f7e-a78e-13b01de72db0@yahoo.com> (raw)
In-Reply-To: <733e9c10-7e3d-4143-8e49-b8ac857d1f8a@yahoo.com>

...

"name": "User-Agent",
"value": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) 
Gecko/20100101 Firefox/146.0"
-cab



On 12/29/2025 12:00 PM, Charles Brown wrote:
> Hello,
> Ugh, no es bueno
>
> Still getting ...
> 404 Forbidden
> You don't have permission to access this resource.
>
> Tried with both
> Firefox Version 146.0.1
> Chrome Version 143.0.7499.170
> on Windows 11
>
> -cbrown
>
> On 12/29/2025 8:02 AM, Michael Tremer wrote:
>> Hello,
>>
>> I change the UA filter. Could you please try again and let me know if 
>> this is resolved?
>>
>>
>> -Michael
>>
>>> On 28 Dec 2025, at 21:17, Matthias Fischer 
>>> <matthias.fischer@ipfire.org> wrote:
>>>
>>> On 28.12.2025 17:00, Michael Tremer wrote:
>>>> Hello,
>>>>
>>>>> On 28 Dec 2025, at 15:53, Matthias Fischer 
>>>>> <matthias.fischer@ipfire.org> wrote:
>>>>>
>>>>> On 28.12.2025 12:23, Michael Tremer wrote:
>>>>>> Hello Matthias,
>>>>> Hi Michael,
>>>>>
>>>>>> Sorry for not replying sooner.
>>>>> No problem...its chrismas and new year and a lot of holidays after
>>>>> all... ;-)
>>>> Exactly. I had a lot of food to eat.
>>> Oh my..you were forced! Poor boy...you have my deepest sympathy... ;-))
>>>
>>>>>> I have applied some protection against the AI bots to 
>>>>>> git.ipfire.org <http://git.ipfire.org/>.
>>>>>>
>>>>>> The VM that this is running on used to have 16 CPU cores and 64 
>>>>>> GiB of memory and was causing so much load that the host system 
>>>>>> started to slow down. This was also caused by a large cache on 
>>>>>> disk that was written to a lot, but rarely accessed again.
>>>>>>
>>>>>> Therefore I added a User-Agent filter that filters out anything 
>>>>>> that is called a “bot”, “crawler”, etc. This allowed that the 
>>>>>> load average of the VM went down from > 180 to something <1.
>>>>>>
>>>>>> What browser are you using and what is the User-Agent it is sending?
>>>>> At the moment I'm using Firefox 146.0.1 - User-Agent should be
>>>>> 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101
>>>>> Firefox/146.0'
>>>> Ah that explains it. I blocked everything containing ‘Windows NT’ 
>>>> because I thought it was a fake UA.
>>>>
>>>> I am currently not at my desk but will remove the filter as soon as 
>>>> I am back
>>> Interesting - I was wondering what happened. Take your time, I'm in no
>>> hurry. ;-)
>>>
>>> Best
>>> Matthias
>>>
>>>>> [Sorry, its still Windows 10 - I still have to persuade my Dell 
>>>>> 7910 to
>>>>> get along with Windows 11... ;-)]
>>>>>
>>>>> All the best
>>>>> Matthias
>>>>>
>>>>>> -Michael
>>>>>>
>>>>>>>> On 27 Dec 2025, at 13:20, Matthias Fischer 
>>>>>>>> <matthias.fischer@ipfire.org> wrote:
>>>>>>> Hi Adolf,
>>>>>>>
>>>>>>> I got no browser cache in my firefox... ;-) - all deactivated. 
>>>>>>> The only
>>>>>>> cache is the 'squid'-memory-cache on my IPFire. And I already 
>>>>>>> restarted
>>>>>>> this one - no improvement: "You don't have permission to access 
>>>>>>> this
>>>>>>> resource."
>>>>>>>
>>>>>>> What I did until now:
>>>>>>>
>>>>>>> Started one of my "Devels".
>>>>>>> 'git checkout next' and 'git pull origin next' is working fine, no
>>>>>>> problems. Ok. Fine.
>>>>>>>
>>>>>>> Started a SSH-connection with 'Far manager' -
>>>>>>> 'mfischer@people.ipfire.org' asks for password, connection is 
>>>>>>> ok, I can
>>>>>>> access '/pub/sources/source-2.x', no problems.
>>>>>>>
>>>>>>> So 'people.ipfire.org' and accessing the sources is working - 
>>>>>>> the only
>>>>>>> thing that doesn't work is GIT per browser and https... I can 
>>>>>>> live with
>>>>>>> that for the moment.
>>>>>>>
>>>>>>> I only wonder why these mails doesn't show up on the list. I'm 
>>>>>>> sending
>>>>>>> them CC, but I can't see them.
>>>>>>>
>>>>>>> Best
>>>>>>> Matthias
>>>>>>>
>>>>>>> On 27.12.2025 13:10, Adolf Belka wrote:
>>>>>>>> Hi Matthias,
>>>>>>>>
>>>>>>>> Only thing I can think of is that there was a problem, which 
>>>>>>>> got fixed
>>>>>>>> or resolved itself but you have the faulty connection now in your
>>>>>>>> browser cache.
>>>>>>>>
>>>>>>>> Maybe try clearing your browser cache and try again.
>>>>>>>>
>>>>>>>> If that doesn't work, I don't have any other thoughts right 
>>>>>>>> now. You
>>>>>>>> will then have to wait for a response from Michael or Rico.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Adolf.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 27/12/2025 02:23, Matthias Fischer wrote:
>>>>>>>>> On 27.12.2025 00:31, Adolf Belka wrote:
>>>>>>>>>> Hi Matthias,
>>>>>>>>> Hallo Adolf, ;-)
>>>>>>>>>
>>>>>>>>> see my comments below...
>>>>>>>>>
>>>>>>>>>> On 26/12/2025 20:06, Matthias Fischer wrote:
>>>>>>>>>>> Hi Michael,
>>>>>>>>>>>
>>>>>>>>>>> sorry for this, but since the mail below can't still be seen 
>>>>>>>>>>> on the
>>>>>>>>>>> list, I don't know if everything is working as it should - 
>>>>>>>>>>> so I'm
>>>>>>>>>>> sending it directly to you. Just FYI only... ;-)
>>>>>>>>>> I can see both of your mails on the development list.
>>>>>>>>> I can see none of mine.
>>>>>>>>>
>>>>>>>>>>> All the best for now and the next year!
>>>>>>>>>>> Matthias
>>>>>>>>>>>
>>>>>>>>>>> -------- Forwarded Message --------
>>>>>>>>>>> Subject: GIT has had enough and is no longer interested. 
>>>>>>>>>>> Thats it!
>>>>>>>>>>> Date: Fri, 26 Dec 2025 14:01:51 +0100
>>>>>>>>>>> From: Matthias Fischer <matthias.fischer@ipfire.org>
>>>>>>>>>>> To: IPFire: Development-List <development@lists.ipfire.org>
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> sorry to interrupt any preparations for new year, but GIT 
>>>>>>>>>>> doesn't like
>>>>>>>>>>> me (or us?) anymore:
>>>>>>>>>>>
>>>>>>>>>>> Since two days https://git.ipfire.org/ leads to:
>>>>>>>>>>>
>>>>>>>>>>> "Forbidden
>>>>>>>>>>>
>>>>>>>>>>> You don't have permission to access this resource."
>>>>>>>>>> I am getting access to the git repo via your link without any 
>>>>>>>>>> of those
>>>>>>>>>> warning messages.
>>>>>>>>> Hm. I still have "no permission to access this resource".
>>>>>>>>>
>>>>>>>>>> Either the problem has been fixed or you are experiencing an 
>>>>>>>>>> issue not
>>>>>>>>>> related to the infrastructure itself.  Hopefully it is the 
>>>>>>>>>> former.
>>>>>>>>> Nope. No change.
>>>>>>>>>
>>>>>>>>> I'll wait. New year, new luck. It won't be long now...
>>>>>>>>>
>>>>>>>>> Best
>>>>>>>>> Matthias
>>>>>>>>>
>>>>>>>>>> Guten Rutsch.
>>>>>>>>> Danke - ebenso! ;-)
>>>>>>>>>
>>>>>>>>>> Adolf.
>>>>>>>>>>> Just for the records... ;-)
>>>>>>>>>>>
>>>>>>>>>>> Best regards and all the best for the new year...!
>>>>>>>>>>>
>>>>>>>>>>> Matthias
>>
>>


  reply	other threads:[~2025-12-29 18:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-26 13:01 Matthias Fischer
2025-12-26 19:06 ` Fwd: " Matthias Fischer
2025-12-26 23:31   ` Adolf Belka
2025-12-27  1:23     ` Matthias Fischer
2025-12-27 12:10       ` Adolf Belka
2025-12-27 13:20         ` Matthias Fischer
2025-12-28 11:23           ` Michael Tremer
2025-12-28 15:53             ` Matthias Fischer
2025-12-28 16:00               ` Michael Tremer
2025-12-28 21:17                 ` Matthias Fischer
2025-12-29 14:02                   ` Michael Tremer
2025-12-29 18:00                     ` Charles Brown
2025-12-29 18:23                       ` Charles Brown [this message]
2025-12-30 15:37                     ` Matthias Fischer
2025-12-31 17:41                       ` Michael Tremer
2025-12-31 18:11                         ` Matthias Fischer
2026-01-02 10:21                           ` Michael Tremer
2025-12-31 21:15                         ` Charles Brown
2026-01-02 10:21                           ` Michael Tremer

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=05288ccc-a274-4f7e-a78e-13b01de72db0@yahoo.com \
    --to=cab_77573@yahoo.com \
    --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