Open shepmaster opened 7 years ago
After some amount of time, this works.
It's seems 'strictSSL: true,' affect, like curl use strict SSL mode will fail
This should not have been closed just because "eventually" after retrying a number of times it finally works. If all software only had to work to those standards, none of us would even use our computers, LOL.
I'm also on Win7x64 and EVERY time I open Atom, and open the settings tab, I am greeted with TWO of these messages:
Fetching outdated packages and themes failed.
Request for package information failed: read ECONNRESET
Only upon waiting (as you indicated) then MANUALLY clicking the "check for updates" button, do these TWO GLARING RED ERRORS get superseded by a success. Of note, these TWO GLARING RED ugly error boxes will NEVER disappear or clear out unless manually clicked the "X" to do so.
I believe this is simply an issue with the SSL as someone below also indicated, but should probably be left open (I request this issue reopened) until the actual root cause is addressed and fixed.
After some amount of time, this works.
For reference, I meant "after waiting the weeks after opening the original issue, I can no longer reproduce the problem". It's entirely possible that what you are experiencing is different, but I've reopened it in case it's useful for the maintainers.
Happening here as well. No proxy, just ECONNRESET
After doing some digging,
{"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}
The issue was noticed after an update to atom. Persisted after a rollback to a previous version. I can't say that it hasn't been a problem for a while.
EDIT: Also, just to be safe, I set strict-ssl
to false in the apm config. Didn't help.
OS: Ubuntu 16.04
~$ apm --version
apm 1.19.0
npm 3.10.10
node 6.9.5 x64
atom 1.26.0
python 2.7.12
git 2.7.4
~$ atom --version
Atom : 1.26.0
Electron: 1.7.11
Chrome : 58.0.3029.110
Node : 7.9.0
just happened to me, but in my opinion this has something to do with network problems. I was connected to wi-fi and this case happened, but because I was in a hurry I changed the connection to 4g and the problem solved
When trying to install the language-rust package, I keep getting this error:
My searching seems to indicate that this is normally caused by failing to configure a proxy server. However, I do not have a proxy server:
I have disabled the Windows Firewall and Windows Defender, but neither had any observable change (I have since re-enabled these). I am running this on a Microsoft-provided VM, but every other network connection has worked just fine! Installing packages through the GUI even worked, before I wiped this VM and re-created it.
I see that apm 1.15 has been released, but for the life of me I cannot figure out how to update it, so I have been unable to try that.
The complete installation output when using
--verbose
: