Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git-proxy failing with DNS Resolution Error for github.com #724

Open
hemantsharma90 opened this issue Oct 1, 2024 · 2 comments
Open
Assignees
Labels
bug Something isn't working question Further information is requested

Comments

@hemantsharma90
Copy link

Hello Team,

I have been trying to execute git-proxy utility in our company environment which is sitting behind a Proxy Server.

Doing a standalone curl works fine with 'https://github.com' as the http_proxy/https_proxy environment variables are already set.

$ curl -kv https://github.com // Success and gives back an HTTP 200

However using the git-proxy utility and running the server via npx.

$ npx -- @finos/git-proxy --config ../new-folder/proxy.config.json
Service Listening on 8080
Listening on 8000

On doing a git push for my repository, I'm getting a DNS Resolution error.

recieved
action processed
Error: getaddrinfo ENOTFOUND github.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

Please note I have also setup up the 'npm config' variables for the company proxy server with the below commands

$npm config set proxy 'http://<proxyuser>:<proxysecret>@<proxyserverhost>:<proxyserverport>'
$npm config set https-proxy 'http://<proxyuser>:<proxysecret>@<proxyserverhost>:<proxyserverport>'

image

@JamieSlome JamieSlome added bug Something isn't working question Further information is requested labels Oct 1, 2024
@JamieSlome JamieSlome self-assigned this Oct 2, 2024
@JamieSlome
Copy link
Member

@hemantsharma90 - thanks for raising the ticket. I'll take a look at your issue today and see if I can establish what is going on 🙌

@hemantsharma90
Copy link
Author

Thanks @JamieSlome . Please let me know if you want me to try any step. Not sure if this could be related to nodejs not doing the dns resolution using a proxy server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants