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
Failed to download `melpa' archive. #2139
Comments
Update. I discovered the problem, and this particular bug report was helpful in finding the solution. It would be nice if emacs was more forgiving in this regard. |
Aha! Glad you tracked it down. |
That is a bit odd.
|
I presume |
I have the same issue just now. |
@s-kostyaev seeing the same issue, too. Can't get the debugger to kick in, but have these messages:
No idea what the archive is supposed to look like - but this is showing up empty?
Is that right? Compare with:
|
@mfine same error too |
I also had the same issues when I tried a couple of hours ago. |
Installed fresh Ubuntu 16.04 yesterday. Nightly build of GNU emacs 25.1.50.2 and installed emacs through the quick install (cloning repo into ~/.emacs.d). It worked fine yesterday. Today, nothing has changed in my emacs version, the spacemacs version or anything else, but I get the error described in this thread. Something gone wrong the the melpa archive? |
UPDATE Ran Now it works |
@eldamir maybe, I upgraded openssl(1.0.2h) though homebrew(osx) today. |
Looks like it's back up:
|
sorry for the downtime. the server is doing a full rebuild. i suspect that the issue with archive-contents may have been related to our server running low on disk space. will spend some time soon working on making the maintenance more automated. |
@milkypostman Thanks for sorting that out. Maybe we should put monit on the build servers and have it alert us when a certain threshold of disk usage is exceeded? |
@milkypostman Same issue yesterday and today. Any thoughts welcomed. Thanks |
@lascott This particular error message is generally not a problem with MELPA, but rather can result from a number of problems with your Emacs setup, most commonly with proxy settings or SSL setup (e.g. openssl version, gnutls). Please check out #3914, which is a more recent ticket about the same error message, and try some of the tests there in order to debug the issue on your machine. |
Had this problem today in Windows 10 (...yeah, I know...) and folks having to update their ssl libraries gave me the idea of having Emacs connect to |
I see this right now. I'm trying to install
I can open 'https://melpa.org/packages/' and 'https://melpa.org/packages/archive-contents' in my browser. |
@achikin it would help if we knew what the error you’re seeing is. |
@achikin You're not following our instructions, though. The problem is most likely that your Emacs doesn't support https, but seeing the error message would help. |
@purcell @milkypostman you were right. I forgot |
package refresh contents |
For anyone who might come across this thread because of the same error: I had the issue. In my init file it wasn't https instead of http though, that bit was missing completely , with the URL essentially being just "://melpa.org/packages/". As soon as I prepended 'http' the error went away |
I'm hitting this, |
Same issue as above |
Edit: looks like the hosting provider is on some gnu/melpa blacklist. Fix: Why does gnu fail as well?
GNU Emacs 26.1 |
I hit this problem on Rasberry Pi OS, Debian Buster. and then added this to the top of my init.el file It fixed the issue. I followed the advice from here https://emacs.stackexchange.com/a/51772 |
I had this problem as well and while I was not able to resolve it (😿) some things that may help others:
|
Have the same issue, although using |
@ertpoi could you provide a description of your particular problem? |
Can I use both |
Had the same issue, removing the trailing slash resolved it: |
with the following line enabled in my init.el, I receive the message:
Failed to download `melpa' archive.
I can download the package list and install packages from melpa-stable.
The text was updated successfully, but these errors were encountered: