brianbrifri

Members
  • Posts

    48
  • Joined

  • Last visited

brianbrifri's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. Yup. Looks like it was a Plex specific issue and not a docker build issue. Remove the tag for the specific version and apply (if you rolled back to the previous version) and then check for updates (those who have not rolled back to the previous version just need to do this). Latest version fixes the issue.
  2. I think something is just broken with that build
  3. That worked. Weirdly it seems that version is actually the same as the latest version, which I assume is having issues.
  4. Are you able to roll back to a previous version?
  5. Hello, I just updated to the most recent docker version: Container ID 04de605cabe4 and am getting errors: Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory 2019-08-26 11:15:29,351 DEBG 'plexmediaserver' stderr output: Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory 2019-08-26 11:15:29,357 DEBG 'plexmediaserver' stderr output: Plex Plug-in [com.plexapp.agents.htbackdrops]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory I've researched the error online and most common fix was to export LD_LIBRARY_PATH=/usr/lib/plexmediaserver. I added that to the docker config but the errors still persist. Any thoughts on what might be the issue?
  6. Yup. .06 Bitcoin, or about $500 at the time, just when it spiked lol I did buy the Bitcoin but never paid the ransom... Now I'm down to half the value it was when I bought it
  7. No problem! It was definitely uploaded (or erased and they lied). Symmetrical Gigabit Internet problems haha
  8. Lol! 1. I did not recover my data 2. Definitely an accident 3. Put unraid ip in the dmz like an idiot 4. Haven't setup pfsense yet It was not an easy password. It was either brute forced or there is some security flaw in SSH they exploited. I kept turning SSH off in unraid but they were able to keep turning it back on somehow. I don't think unraid blocks further SSH attempts after several failed ones?
  9. I run it with Nord VPN just fine. Use custom VPN provider from drop down
  10. Yup, I'm thinking it was a isp or VPN issue
  11. Mine works with VPN now too....no shaggy what's going on here either.
  12. Hmmmmm was able to get it to work by disabling VPN. I didn't work with it disable last time but I just upgraded my unRAID version to 6.6.6. Will try messing with VPN stuff then report back
  13. @binhex Here is my supervisord.log file (I removed sensitive info and cert stuff only) supervisord.log