Forum Discussion

Tutor

Dec 31, 2016

Solved

PLEX Install error RN104

Hi, I know there have been a lot of issues with plex on the latest OS6.6. im having an issue installing the latest plex and not sure if its related, this is the error from debpkg log Successfully...

Netgear Apps & Add-ons

Plex

Sandshark
Dec 31, 2016
hawke84 wrote:
Hi, I know there have been a lot of issues with plex on the latest OS6.6. im having an issue installing the latest plex and not sure if its related, this is the error from debpkg log

Successfully installed dependencies for /tmp/plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb
dpkg: error processing archive /tmp/plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb (--install):
cannot access archive: No such file or directory

any thoughts?
Did you copy that directly from the log, or is it possible that it actually says something like error processing archive /tmp/C:plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb (--install): ?

I've seen it include the drive letter and directory of the source .deb package in the log entries, and it always fails when it does (because a package by that name doesn't exist). The solution has been to clear the browser cache, close and re-start browser, and re-retry. Even if it doesn't show that, it may be worth a shot. Clearly, there is a problem sometimes passing the package name, and you may have run into something a little different than I have but still related.

Sandshark

Sensei - Experienced User

Dec 31, 2016

hawke84 wrote:
Hi, I know there have been a lot of issues with plex on the latest OS6.6. im having an issue installing the latest plex and not sure if its related, this is the error from debpkg log

Successfully installed dependencies for /tmp/plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb
dpkg: error processing archive /tmp/plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb (--install):
cannot access archive: No such file or directory

any thoughts?

Did you copy that directly from the log, or is it possible that it actually says something like error processing archive /tmp/C:plexmediaserver-ros6-binaries_1.2.6.2975-9394c87_armel.deb (--install): ?

I've seen it include the drive letter and directory of the source .deb package in the log entries, and it always fails when it does (because a package by that name doesn't exist). The solution has been to clear the browser cache, close and re-start browser, and re-retry. Even if it doesn't show that, it may be worth a shot. Clearly, there is a problem sometimes passing the package name, and you may have run into something a little different than I have but still related.

hawke84

Tutor

Jan 01, 2017

thank you this got me on the right lines. tried it with internet explorer and it uploaded fine. seemed to be an issue with chome

Dave338
Aspirant
Jan 11, 2017
Please hawke84, could you explain me step by step how did you manage to install and run plex on the RN104??

I have tried it many times, and it installs apparently fine and executes, but when I enter plex web with my user, I can't see the PMS on the NAS, I only see other PMS for Windows that I have installed... something is missing but I don't know what.

Regards.
- hawke84
  Tutor
  Jan 11, 2017
  Hi, when i did the upload and installw ith chrome it didnt work. using internet explorer allowed the upload and install.
  
  1. go to https://www.plex.tv/downloads/
  2. click download, and select netgear, click on download and select ARM 6.x
  3. Save the file to your PC
  4. log into the admin panel on the RN104 using internet explorer
  5. click on apps and do manual upload
  6. find the plex file ending in .deb that you downloaded
  7. it will upload and install
  8. reboot the NAS
  9. toggle plex on under apps. should be running fine.
  10. setup as normal.
  
  hope this helps
  - Dave338
    Aspirant
    Jan 11, 2017
    Thanks hawke.
    
    I thought that you addedsome files or something manually, but I must be mistaken, heheh
    
    This is the exact procedure I did, and it didn't worked for me.
    I'll try again with new firmware 6.6.1 to see if something has been fixed... :(
    
    Regards.