Debian machine with "jessie-backports" no longer have release file

Today I get this message when trying to run apt update on my Debian:

Hit:1 stretch/updates InRelease
Ign:2 stretch InRelease
Hit:3 stretch-updates InRelease
Hit:4 stretch Release                                            
Ign:5 jessie-backports InRelease                                           
Err:6 jessie-backports Release                         
  404  Not Found [IP: 80]
Get:7 stretch InRelease [2,520 B]                     
Get:8 stretch InRelease [6,760 B]              
Hit:9 stretch InRelease
Get:10 stretch InRelease [4,635 B]
Hit:11 main InRelease
Err:8 stretch InRelease      
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
Reading package lists... Done 
E: The repository ' jessie-backports Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743

Any help will be much appreciated :)


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello, I got a similar problem, but not for the backports, but for this four:

W: Failed to fetch  404  Not Found [IP: 80]

W: Failed to fetch  404  Not Found [IP: 80]

Err jessie-updates/main Sources
  404  Not Found [IP: 80]

Err jessie-updates/main amd64 Packages
  404  Not Found [IP: 80]

Is there some help on that one?

@jarland I see. Thank you for your answer.

What would be the best thing to do from now for existing Droplets? Shall we totally delete them and move data to a new one? Any upgrade path your team is aware of?

Hi @jarland and thank you for your answer.

I don’t think that’s my responsability to update source list because, as you can see, Debian-based Droplets rely on Digital Ocean mirrors:

# See
deb stretch main contrib non-free
deb-src stretch main contrib non-free

# Major bug fix updates produced after the final release of the distribution.
deb stretch/updates main contrib non-free
deb-src stretch/updates main contrib non-free
deb stretch-updates main contrib non-free
deb-src stretch-updates main contrib non-free

Is Digital Ocean team working on something to fix this situation?


The Debian team has disabled the Jessie backports repository. I do not believe that they intend to update it further, but I’m told that you can continue to use the archive of the repository by changing “” to “” in your apt source list.