From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dfH6544hdz332Q for ; Sun, 28 Dec 2025 11:23:25 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dfH616cDrz2xHk for ; Sun, 28 Dec 2025 11:23:21 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dfH5z24s2zV3; Sun, 28 Dec 2025 11:23:19 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1766920999; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Tcqg/PcBzQ6exMbi6nxleLf2uPTTM2ryXBYrPk7oDMI=; b=467h+aKjphCaMs5UQH9GS1ubfIweDXxs+I1gjFBE+UArtiSxlsPGz0DpZCWBH9vL38woyO n+7+z6rhNo26kVAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1766920999; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Tcqg/PcBzQ6exMbi6nxleLf2uPTTM2ryXBYrPk7oDMI=; b=tF5mTifO5xuiLTttMKmLhHRT/qV0zYnxRHVfmLs5ObEe4m7MJG7NTxp0NnZZhvl2fIRvEf vloZRNwLEJEJaDl3djbNarIZCyysag4YQBGWTI3Z40gmOi9gYEgZUE2iQ+CBcEH+Oft03l EvxppehQQxzBvtwAwomonQUXlDqj5wmYeCnIFEXxbmOKY5OgBZJkLk2PIA+2hSirJYTBtC 4ISKd9he5XPe6a2DTw+zrx4LnC2R1SMLNdz5sQeCV5sW/pGR3emXVz5fUG3bXkx8Dc+ybL jMGMm116Se3W3GjV+9hQNd/5BbcVU5PdGpKJirJ7rWMh/Wrz/xX7k/r2jVreQQ== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: GIT has had enough and is no longer interested. Thats it! From: Michael Tremer In-Reply-To: Date: Sun, 28 Dec 2025 11:23:18 +0000 Cc: Adolf Belka , "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <2F35A7C3-79C9-4E74-BDD7-0F9B686D7022@ipfire.org> References: <9ef4f1dc-57f8-4926-a722-543a170f77e7@ipfire.org> To: Matthias Fischer Hello Matthias, Sorry for not replying sooner. I have applied some protection against the AI bots to 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 =E2=80=9Cbot=E2=80=9D, =E2=80=9Ccrawler=E2=80=9D, 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? -Michael > On 27 Dec 2025, at 13:20, Matthias Fischer = wrote: >=20 > Hi Adolf, >=20 > 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." >=20 > What I did until now: >=20 > Started one of my "Devels". > 'git checkout next' and 'git pull origin next' is working fine, no > problems. Ok. Fine. >=20 > 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. >=20 > 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. >=20 > I only wonder why these mails doesn't show up on the list. I'm sending > them CC, but I can't see them. >=20 > Best > Matthias >=20 > On 27.12.2025 13:10, Adolf Belka wrote: >> Hi Matthias, >>=20 >> Only thing I can think of is that there was a problem, which got = fixed=20 >> or resolved itself but you have the faulty connection now in your=20 >> browser cache. >>=20 >> Maybe try clearing your browser cache and try again. >>=20 >> If that doesn't work, I don't have any other thoughts right now. You=20= >> will then have to wait for a response from Michael or Rico. >>=20 >> Regards, >>=20 >> Adolf. >>=20 >>=20 >> On 27/12/2025 02:23, Matthias Fischer wrote: >>> On 27.12.2025 00:31, Adolf Belka wrote: >>>> Hi Matthias, >>> Hallo Adolf, ;-) >>>=20 >>> see my comments below... >>>=20 >>>> On 26/12/2025 20:06, Matthias Fischer wrote: >>>>> Hi Michael, >>>>>=20 >>>>> 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. >>>=20 >>>>> All the best for now and the next year! >>>>> Matthias >>>>>=20 >>>>> -------- 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 >>>>> To: IPFire: Development-List >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> sorry to interrupt any preparations for new year, but GIT doesn't = like >>>>> me (or us?) anymore: >>>>>=20 >>>>> Since two days https://git.ipfire.org/ leads to: >>>>>=20 >>>>> "Forbidden >>>>>=20 >>>>> 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". >>>=20 >>>> 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. >>>=20 >>> I'll wait. New year, new luck. It won't be long now... >>>=20 >>> Best >>> Matthias >>>=20 >>>> Guten Rutsch. >>> Danke - ebenso! ;-) >>>=20 >>>> Adolf. >>>>> Just for the records... ;-) >>>>>=20 >>>>> Best regards and all the best for the new year...! >>>>>=20 >>>>> Matthias >>>>>=20 >>>>>=20 >>>=20 >>=20 >=20 >=20