-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Error: connect ECONNREFUSED 127.0.0.1:443 for downloading a binary #615
Comments
I don't have permission to push so I can't create a PR: |
this is to be expected, unless you are a maintainer of this package (eg have
this understanding is wrong, this function returns a string, but
it seems like your request was forwarded to the localhost ip and https port, which very likely does not exist, or is at least not what is expected things you can do / check:
Note: i do not know how Mac systems operate, so i cannot help in more detail Also this issue seems to be related to #600 (where no more information was given and then closed, this issue here (#615) will remain open as a continuation) PS: i changed the title to better reflect what this issue is about |
Thank you for your reply!
No firewall
No other firewall (that I know of). This issue also happens to other colleagues (on mac M1) as well, and we are all working from home from different cities.
I don't
I'm not running it in a sandbox - running it on my work mac with a residential ISP, nothing special router, no container
I updated to v16.14.0 (latest LTS) and the same issue occurs
If I look at the docs from nodejs, string is listed as a param first, so I'd expect that a string is preferred (from a node perspective) - but I'm definitely not sure. The issue also persists in our CI/CD platform which uses the basic node docker image |
see docs: in our case could you maybe give me the output of #600 (comment) ? (placed in the MMS node_module on your system, just before this line(s)) |
Thanks again for the reply - after I added the comment, it works now. So weird because I did not change anything. The code (same code) also works in our CI/CD. I'll confirm with my colleagues to see if it works for them again. I think the only change that I've done is:
|
definitely weird if i understand correctly, you dont have the error anymore and cannot reproduce it anymore? if so, i would close this again because of insufficient information |
That error happens repeatdly in gitlab-ci node: 'v16.15.0'
but whenever I clear the gitlab CI cache, and retry manually the job, it works What's annoying is when another job is later automatically ran, for some reason it'll fail again But I think it's more a gitlab issue than this package, just leaving this here for the record |
this can be related to other libraries, try to debug and find breaks it. For me it was old |
Just in case you stumble across this. For us the culprit was an old node-agent-base dependency (Related Issue). Looks like it's patching some basic node functions, which breaks (or broke) a lot of libraries. In our case this dependency was installed due to an old mailgun-js version (thanks @pavlonadolynskyi for the hint). We migrated from mailgun-js to mailgun.js and the problem went away. Edit: |
Versions
package: mongo-memory-server
What is the Problem?
It's not possible to start a mongoServer as an error on the https.get call to the mongodb binary happens 100% of the time, if you don't have the binary installed locally.
I've tried different MongoMemoryServer versions (4.2.8, 5.0.3) etc. Accessing the link directly (via browser) works and installs the binary (As expected, see why I think it happens)
Error:
Couldnt download "https://fastdl.mongodb.org/osx/mongodb-macos-x86_64-5.0.3.tgz"! connect ECONNREFUSED 127.0.0.1:443
Code Example
Debug Output
Debug Output
Do you know why it happens?
The correct URL is created (
const downloadUrl = this.assignDownloadingURL(url);
) but is not used later by the actual HTTPS request here.The text was updated successfully, but these errors were encountered: