OK, so I started off creating my own local Debian repository. Not recommended -- it's a lot of work. But with a lot of Googling and experimenting, I finally got apt to work using an online source. Now, this requires bypassing a lot of security features, so use at your own risk. It works on ARM and Intel based systems. My /etc/apt/sources.list now looks like this:deb https://apt.readynas.com/packages/readynasos 6.10.8 updates apps main # deb http://mirrors.kernel.org/debian jessie main # deb http://security.debian.org/ jessie/updates main deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie main contrib non-free deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie-backports main contrib non-freeI commented out two original lines, but you can remove them if you like. archive.kernel.org is a US repository, so you can look for another if you like. Netgear never had a jessie-backports source or contrib and non-free included for jessie, so you may not want them. Then you need to create /etc/apt/apt.conf with the following content:Get::AllowUnauthenticated true; Acquire::Check-Valid-Until false;How long will this last? I don't know, but that archive has some distros even older than Jessie, so I suspect for a while.

OK, for those still struggling to follow the whole thread or having difficulty with VI or trying to use a Windows editor, here is a summary and quick solution: This is my current /etc/apt/sources.list with firmware 6.10.9:deb https://apt.readynas.com/packages/readynasos 6.10.9 updates apps main # deb http://mirrors.kernel.org/debian jessie main # deb http://security.debian.org/ jessie/updates main deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie main contrib non-free deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie-backports main contrib non-free deb [trusted=yes] http://archive.debian.org/debian-security jessie/updates main non-free contrib /etc/apt/apt.conf remains unchanged for my original post:Get::AllowUnauthenticated true; Acquire::Check-Valid-Until false; Now, if you are having trouble getting them this done, here is a solution. Note that these files are from my personal DropBox, so may disappear after a few months. You still need SSH, but don't have to edit anything. https://www.dropbox.com/scl/fi/zoqxg8u1y0ztqjkfrvod7/sources.list?rlkey=5ouaymaz3ejn0ssc58ad8nfrk&dl=0 https://www.dropbox.com/scl/fi/25hs7nn12830vz9xk2phx/apt.conf?rlkey=maf95f9ncug9q09v4znm0kiwt&dl=0 Put these somewhere on your NAS using SMB, the GUI, or whatever. Then, from SSH, you simply need to copy them from where you put them to their proper place. Then do an apt-get update (Note: NOT upgrade!). When you do so, these are the only warnings you should see:W: GPG error: http://archive.kernel.org/debian-archive/debian jessie-backports InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673 W: GPG error: http://archive.kernel.org/debian-archive/debian jessie Release: The following signatures were invalid: KEYEXPIRED 1587841717 Well, those are the only ones unless an app has put something in /etc/apt/sources.list.d, in which case you may have to add [trusted=yes] there as well.And once you get this done, run apt-get install nano to get yourself a usable editor. If you are sticking with ReadyNAS, there's a good chance you'll need it down the road.

Hi All, After going back and re-reading this and the ZeroTier as ReadyCloud Replacement threads, I finally got 1.6.6 running and online! It totally works! I see the remote server in the macOS network tab and I can log on with my credentials and everything I expect is there. It's a fine replacement for ReadyCloud and the team is stoked to be able to work remotely again. Thanks Sandshark, StephenB, and everyone else for your help!😊

I'm glad it worked for you. I have no idea why you need the -f option to install nano, but thanks for sharing in case somebody else has an issue with it. But while I don't like making excuses for Netgear, they are actually doing the right thing not making this a part of an OS update. Setting it to allow unauthenticated sources is a (small, and IMHO acceptable for home use) potential security hole. Users need to choose for themselves whether or not it's acceptable to them. Of course, with 6.10.10, they decided to go the other direction and prevent users from deciding to allow it, which is unacceptable. Of course, they should have upgraded ReadyNAS OS to a newer Linux base a long time ago, but now I wonder if they haven't been planning this exit from the NAS business for a while, and that's the reason they didn't do it.

FYI, the keys in the debian archives are beginning to expire. You need to add this to apt.conf to overcome that problem: Acquire::Check-Valid-Until false;

It's not a command, it's an edit to etc/apt/sources.list . One issue here is that the only editor installed on a ReadyNAS by default is VI, which is a true PITA to use. You can put a copy in a folder accessible from Windows and use an editor there that doesn't mess with the EOL character(s) such as NotePad++, but you then also have to deal with ownerships and permissions when you copy it back. Nano is a much easier editor to use from SSH, but you have to have previously installed it or you won't be able to until after you make this edit.

How I got apt update and install to work (with Debian Jessie retired)

92 Replies

tigerten
Luminary
Apr 12, 2023
Great!

Can you find a way to use https:// as source?
- Sandshark
  Sensei
  Apr 12, 2023
  I didn't try initially. But just did, and it does not work. Not sure of the point, anyway, since it's nothing that needs protection from prying eyes.
  
  I forgot to mention in my initial post that you will get some warnings about expired keys, but they are just warnings because you've told the OS to ignore them.
  - StephenB
    Guru
    Apr 13, 2023
    Sandshark wrote:
    
    Not sure of the point, anyway, since it's nothing that needs protection from prying eyes.
    
    https would also verify the cert, and provide protection against a man-in-the-middle attack. So there would be some value if it worked (over and above the encryption)
ArchPrime
Guide
Apr 23, 2023
Hi, I am likely missing the obvious, but as a non-linux user, I used Putty to gain SSH access to my ReadyNAS Ultra6 (running OS6.10), and tried copy pasting the above - but without success:

root@ReadyNAS:~# deb https://apt.readynas.com/packages/readynasos 6.10.8 updates apps main -bash: deb: command not found

What is missing here? Googling this error suggests there is likely a .list file somewhere that needs to be edited or added to, but which of these, and how to do this I don't know. Keen not to destroy anything unnecessarily.

I want to do this as a way to get the docker app working again under OS6, so I can then see if Home Assistant or other potential routes for getting IP camera monitoring software to work are possible on this hardware.
- Sandshark
  Sensei
  Apr 24, 2023
  It's not a command, it's an edit to etc/apt/sources.list . One issue here is that the only editor installed on a ReadyNAS by default is VI, which is a true PITA to use. You can put a copy in a folder accessible from Windows and use an editor there that doesn't mess with the EOL character(s) such as NotePad++, but you then also have to deal with ownerships and permissions when you copy it back. Nano is a much easier editor to use from SSH, but you have to have previously installed it or you won't be able to until after you make this edit.
  - ArchPrime
    Guide
    Apr 24, 2023
    Thanks for that - yes I clearly did miss the obvious!
    
    I encountered the horrors of VI.
    Obviously designed by a committed sadist, or someone to whom the idea of 'user experience' was an incomprehensible concept ; No obvious way to incorporate colons on any line of text - as is required when creating the apt.conf text file - without this being interpreted as an VI editor command.
    
    Ended up doing via FileZilla (which invoked notepad for editing), which avoided any nasty Linux cli stuff, and retains existing file permissions when altered file is resaved.
    
    However with both files now in place, and identical to your examples (via cut and paste), and with ReadyNAS rebooted, I still cannot seem to install the Docker app via the 'Available Apps' menu in OS6.
    
    I also see that after ReadyNAS reboot I am suddenly I am being given 'Not secure' warnings by my browser when accessing ReadyNAS webpage, and the icons previously associated with the available apps in OS6 are now showing as broken links
StephenB
Guru
May 05, 2023
Sandshark wrote:

OK, so I started off creating my own local Debian repository. Not recommended -- it's a lot of work.

FWIW, you can use apt-mirror for this:

https://apt-mirror.github.io/

If you set mirrors.list to

deb https://apt.readynas.com/packages/readynasos 6.10.7 updates apps main deb http://archive.kernel.org/debian-archive/debian jessie main contrib non-free deb http://archive.kernel.org/debian-archive/debian jessie-backports main contrib non-free

you can get all three of these repositories.

The Netgear one is about 4 GiB. You can't copy 6.10.8 because Netgear hasn't set the permissions up properly (no one can access it). Hopefully they will fix that soon.

The two Debian 8 repositories total about 72 GiB.

Note I haven't tried to use these yet, I just mirrored them.
- tigerten
  Luminary
  May 05, 2023
  I would also recommend adding the retired and archived Debian security repo as well.
  
  Http://archive. Debian.org/Debian-security Jessie/updates main non-free contrib
  
  Something like that. The packages there are newer.
  - StephenB
    Guru
    May 06, 2023
    tigerten wrote:
    I would also recommend adding the retired and archived Debian security repo as well.
    
    Http://archive. Debian.org/Debian-security Jessie/updates main non-free contrib
    
    Thx for the tip, I have added that.
    
    One aspect with apt-mirror - it grabs the repository for the platform you are using. So if you are on an x86 machine, it will get the x86 repository.
    
    It will run on the NAS without needing installation, so you can just run it there to make sure you get the repository you need for your platform. Make sure you are saving to the data volume, as the OS partition is far too small.

Gregsta

Aspirant

May 20, 2023

I followed the steps in the first message but see all these kind of errors. Why does apt-get attempt to install the deb8u1 version of these packages if deb8u2 is already installed? This type of error is seen for most package installs.
Looks like something is defaulting to deb8u2 while something else is defaulting to deb8u1 packages...

root@steammills:/data# apt-get install gcc-4.9
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gcc-4.9 : Depends: cpp-4.9 (= 4.9.2-10+deb8u1) but it is not going to be installed
           Depends: gcc-4.9-base (= 4.9.2-10+deb8u1) but 4.9.2-10+deb8u2 is to be installed
           Depends: libgcc-4.9-dev (= 4.9.2-10+deb8u1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

eton
Luminary
May 22, 2023
In my previous post I forgot to add the sources I use. They are:

deb http://archive.debian.org/debian/ jessie main contrib non-free deb http://archive.debian.org/debian-security jessie/updates main contrib non-free

In /etc/apt/sources.list

The backport sources mentioned by Sandshark might be better.

phs989
Aspirant
Jul 04, 2023
Id love to do this change to my ReadyNAS. Im actually trying to install Remote.it but cant due to the lack of jq on the debian platform and errors to upgrade.

Im a total newbie when it comes to this but can use SSH and can connect to my ReadyNAS. Can you help with some more detailed step by steps for me?
- schumaku
  Guru
  Jul 04, 2023
  phs989 wrote:
  
  Id love to do this change to my ReadyNAS. Im actually trying to install Remote.it but cant due to the lack of jq on the debian platform and errors to upgrade.
  
  Start from the two files Sandshark explained to modify resp. add back in April 2023 https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/How-I-got-apt-update-and-install-to-work-with-Debian-Jessie/m-p/2306772/highlight/true#M199238
  
  A little bit to vague on what "Remote" you are asking about....
  - phs989
    Aspirant
    Jul 04, 2023
    Managed to get the 2 files modified and added to the required folder. Sorry youre right the use of remote was vague. This is the service i am trying to set up https://www.remote.it/benefits to enable remote access to my ReadyNAS. Im a basic user of this and mostly my NAS is used for local file sharing but sometimes i need to share with external sources too.
    I managed to run apt-update and it seemed to work but im getting errors when i try and install the remote.it package. Ive sent the error to their support for help.
    Their support told me i needed jq 1.6 and when i checked it states i have jq 1.4-2.1 so i dont understand why this would be an issue?
    jq is already the newest version (1.4-2.1+deb8u1)
Sandshark
Sensei
Jul 24, 2023
OK, for those still struggling to follow the whole thread or having difficulty with VI or trying to use a Windows editor, here is a summary and quick solution:

This is my current /etc/apt/sources.list with firmware 6.10.9:
deb https://apt.readynas.com/packages/readynasos 6.10.9 updates apps main # deb http://mirrors.kernel.org/debian jessie main # deb http://security.debian.org/ jessie/updates main deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie main contrib non-free deb [trusted=yes] http://archive.kernel.org/debian-archive/debian jessie-backports main contrib non-free deb [trusted=yes] http://archive.debian.org/debian-security jessie/updates main non-free contrib

/etc/apt/apt.conf remains unchanged for my original post:
Get::AllowUnauthenticated true; Acquire::Check-Valid-Until false;

Now, if you are having trouble getting them this done, here is a solution. Note that these files are from my personal DropBox, so may disappear after a few months. You still need SSH, but don't have to edit anything.

https://www.dropbox.com/scl/fi/zoqxg8u1y0ztqjkfrvod7/sources.list?rlkey=5ouaymaz3ejn0ssc58ad8nfrk&dl=0
https://www.dropbox.com/scl/fi/25hs7nn12830vz9xk2phx/apt.conf?rlkey=maf95f9ncug9q09v4znm0kiwt&dl=0

Put these somewhere on your NAS using SMB, the GUI, or whatever. Then, from SSH, you simply need to copy them from where you put them to their proper place. Then do an apt-get update (Note: NOT upgrade!). When you do so, these are the only warnings you should see:
W: GPG error: http://archive.kernel.org/debian-archive/debian jessie-backports InRelease: The following signatures were invalid: KEYEXPIRED 1587841717 KEYEXPIRED 1668891673 W: GPG error: http://archive.kernel.org/debian-archive/debian jessie Release: The following signatures were invalid: KEYEXPIRED 1587841717

Well, those are the only ones unless an app has put something in /etc/apt/sources.list.d, in which case you may have to add [trusted=yes] there as well.

And once you get this done, run apt-get install nano to get yourself a usable editor. If you are sticking with ReadyNAS, there's a good chance you'll need it down the road.
- ietsrl
  Aspirant
  Aug 21, 2023
  whats change in apt.conf?
  Thanks
  - StephenB
    Guru
    Aug 21, 2023
    ietsrl wrote:
    
    whats change in apt.conf?
    
    It's actually not in the default ReadyNAS config at all.
    
    Just read the info in the post right above yours...
    
    Then you need to create /etc/apt/apt.conf with the following content:
    
    Get::AllowUnauthenticated true; Acquire::Check-Valid-Until false;
- makkistyle
  Tutor
  Mar 21, 2024
  I loged in and this what shows me :
  
  but the file you mentioned ( apt.conf )
  where.i should copy it ?
  here is a look in the folder apt.conf.d :
  - Sandshark
    Sensei
    Mar 21, 2024
    As stated in the very first message of the thread "Then you need to create /etc/apt/apt.conf with the following content:" So you put it in /etc/apt.
- ChunkySocks
  Guide
  Apr 06, 2024
  Thanks for all contribuors and especially thanks to both StephenB and Sandshark for their continued posting in these forums to help others.
  
  I SSH'd into my ReadyNAS and successfully managed to follow Sandshark's instructions.
  This was after installing 6.10.10 and now that installing/upgrading apps via the GUI is disabled, I can't use that method to update my Plex server plus I also wanted to upgrade my Logitech Media Server to the most recent stable version.
  
  ~~If I download a deb file, where does it need to be put on the NAS and what commands do I need to run when I SSH into the NAS in order to upgrade these programs? Thank you~~.
  
  Think I've worked it out:
  find the correct .deb file, in this case plexmediaserver_1.40.1.8227-c0dd5a73e_amd64.deb
  download to local machine then copy it to a folder on the NAS
  navigate to the directory containing the file
  run sudo dpkg -i plexmediaserver_1.40.1.8227-c0dd5a73e_amd64.deb
  - StephenB
    Guru
    Apr 06, 2024
    ChunkySocks wrote:
    
    Think I've worked it out:
    
    find the correct .deb file, in this case plexmediaserver_1.40.1.8227-c0dd5a73e_amd64.deb
    
    For Plex, go to https://www.plex.tv/media-server-downloads/?cat=computer&plat=windows#plex-media-server and select "Netgear". Then choose the correct distribution for your NAS.
    
    ( ChunkySocks did get the correct download, I'm just adding this for the benefit of future readers).
dhl
Luminary
Sep 18, 2023
Hi All,

After going back and re-reading this and the ZeroTier as ReadyCloud Replacement threads, I finally got 1.6.6 running and online!

It totally works! I see the remote server in the macOS network tab and I can log on with my credentials and everything I expect is there. It's a fine replacement for ReadyCloud and the team is stoked to be able to work remotely again.

Thanks Sandshark, StephenB, and everyone else for your help!😊
- dhl
  Luminary
  Oct 11, 2023
  Hi All,
  
  Recently ZeroTier suddenly stopped working for us. I checked the ZeroTier network and it appears that our ReadyNas is not connecting. Here's a screen shot:
  
  The top address is the ReadyNAS, the bottom address is my connected computer. As you can see, the ReadyNAS doesn't have an IP on the network.
  
  I ran zerotier-cli join in terminal with the network ID and received a 200 OK reply
  But when I run zerotier-cli info I get an OFFLINE reply even though the ReeadyNAS is authorized.
  
  Sandshark, StephenB and anyone else - have you encountered this problem? What do I need to do to get ZeroTier back up and running? I'm using version 1.6.6
  
  I found this discussion in the ZeroTier forum but I'm hoping I don't have to reinstall:
  https://discuss.zerotier.com/t/zerotier-cli-shows-offline-zerotier-gui-shows-connected/138
  
  Things were working great until it broke. Any advice greatly appreciated.
  
  Thanks!
  - Sandshark
    Sensei
    Oct 12, 2023
    What model NAS is this on? I had a similar issue when both of my Ethernet ports were enabled and the primary one didn't have internet access. I have my primary and backup NAS's connected to just each other via a switch and static IP's, but the primary had ETH1 connected to my "real" LAN and ETH0 to the local-only one where the backups had the opposite. Swapping the ports (including their DHCP options) and re-booting the NAS did the trick. If your are using ETH1 as your primary network connection and ETH0 is enabled, even though not connected to anything, perhaps the same thing could happen.
John____
Aspirant
Mar 03, 2024
Thank you.
This let me update Plex Media Server after I let the 6.10.10 update install.on my RN 516.
I'm now back on 6.10.9.with the current Plex Media Server running.
- Langzik_NAS
  Guide
  Mar 14, 2024
  So, John____ , just to clarify [because I'm in the same boat you were in], you're back in 6.10.9 and able to do app updates via the web interface? Or are you doing it over SSH?
  
  I've managed to revert back to 6.10.9 after foolishly upgrading without checking what was being changed (honestly, never in my wildest dreams did I think they were going to purposefully wreck their users this hard), but everything is still broken on my end insofar as updating apps via the web interface is concerned.
  - StephenB
    Guru
    Mar 14, 2024
    Langzik_NAS wrote:
    
    I've managed to revert back to 6.10.9 ... but everything is still broken on my end insofar as updating apps via the web interface is concerned.
    
    Did you re-apply the mods in this thread? They are needed to get most installs to work.
Dankel2
Aspirant
Mar 29, 2024
For Plex app (probably any other app also) if anyone has a ReadyNAS 312 like I do you may want to try and downgrade from 6.10.10 to 6.10.9, reboot and then install/update Plex app from the GUI. This is what I did and I'm working again. All my Available Apps and Installed Apps are back. Worth a try.....
- Sandshark
  Sensei
  Mar 30, 2024
  Just downgrading the OS is sufficient for a Plex update because it needs no new dependencies from the Debian archive. Updates to others likely will be the same, since Debian 8 hasn't been updated in some time. But for most new installations, it's going to need access to the Debian archive to download dependencies, so the changes listed here are required.
Laserbait
Luminary
Apr 11, 2024
Thanks Sandshark ! I got all 4 of my arrays back to 6.10.9, and updated their repos with your info. I appreciate you blazing that trail for us! 🙂