Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

no_proxy doesn't appear to be honoured

See original GitHub issue

Subject of the issue

We are using Github Enterprise with self hosted runners running behind a cooperate web proxy.

The no_proxy value is set, to include the specific host eg github.foo.com and also a .foo.com

Steps to reproduce

I can’t share the workflow, but use the action behind a proxy with the following set for the whole runner: HTTPS_PROXY HTTP_PROXY NO_PROXY

Issue Analytics

State:
Created a year ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

codefish1commented, Dec 14, 2022

Tested it just not and it all appears to be working fine

1reaction

codefish1commented, Dec 12, 2022

Sure, I’ll make some time to look at it later this week. Unfortunately I’m off sick with COVID atm

Top Results From Across the Web

no_proxy environment variable is not getting honored #59

Hi - I am mounting environment variables as spec: serviceAccountName: kubernetes-external-secrets-service-account containers: - image: ...

1990556 – get-resources.sh doesn't honor the no_proxy ...

Hi @kiran: adding the IP in the list of the noProxy variable works as expected. Is expected to allow CIDR in the noProxy...

NO_PROXY ignored by .NET Core 3.0 on Windows

An http.Get in Go appears not to be using the HTTP proxy specified in the HTTP_PROXY environment variable? Hot Network Questions.

Git doesn't honor NO_PROXY environment variable while ...

It seems like Git doesn't honor NO_PROXY environment variable while cloning repositories Reporter has provided these steps to reproduce using Git version ...

apt does not (always) honor the no_proxy environment ...

apt does not (always) honor the no_proxy environment variable ... It seems like the proxy setting is not properly reset for libcurl.