Hi Mark, On Mon, Dec 29, 2025 at 8:16 AM Mark Wielaard <[email protected]> wrote:
On Mon, Dec 29, 2025 at 07:06:51AM -0500, Tom Kacvinsky via Gcc wrote: > > It's back. I suspect it's the same problem I had before, so I asked the > > network administrators at my job to see what address ranges our Zscaler > > endpoint is using to tell you to see if that is an address range that is > > being blocked. It's so frustrating that a company such as the one I work > > for doesn't pull this kind of stuff gets blocked because of some bad > actors. > > Could you provide a bit more info? What operation are you performing, > which outgoing IP address are you using? Are there any specific error > messages? Do you have a reference to what happened before and how it > was resolved back then? > > I am using git pull. I am trying to find the outgoing IP address(es) from my employer's network administrators - I have not heard from them yet. I am using a Linux machine for the request, so I can't see the outgoing IP addresses. If I were using my Windows machine, I could see that through the Zscaler app. But that information is not accessible to me from Linux machines in our DC. If this is using the git http backend you are probably hitting the > issue that we had to disable that for the moment because of bot > attacks (please use the git:// or ssh:// protocol for now): > https://inbox.sourceware.org/[email protected] > https://fosstodon.org/@sourceware I am using the https protocol. Our network administrators have blocked git: and ssh: for egress to repositories as they consider ssh to be a security risk. Tom
