musicking

Members
  • Posts

    61
  • Joined

  • Last visited

Everything posted by musicking

  1. The update went fine for me. Hopefully fixed my crashing issues. FIXES: (Auto Update) Custom install paths are not respected when auto-updating on 64 bit Windows. (PM-1143) (CreditsDetection) Retry detection only a limited amount of times on failures (PM-1093) (DB Optimize) Server could become unresponsive during a DB optimize in certain circumstances (PM-1129) (Loudness Analysis) Some files could cause errors when preforming Loudness Analysis. (PM-627) (Push Notifications) Used expensive DB query during playback progress notifications (PM-1166) -- This could have been my issue (Thumbnails) Thumbnails were not properly updated when underlying file changed (PM-1162) (Transcoder) On Windows, headless (no display attached) Nvidia cards were not recognized (PM-962) (Transcoder) On Windows, the first Intel device was used for transcoding regardless of which Intel device was selected (PM-962)
  2. Removed the user that was using the Roku client and so far, my Plex has remained stable.
  3. F, my Plex is still crashing and the only pattern I see is when someone with an old Roku client connects it crashes. Was fine a few days and then the Roku client connects and it crashes.
  4. I suspect there are some Plex bugs in the last couple of builds that need to be worked out. I have had 0 issues with Plex and this docker for years. The last time I had issues, it was Plex related and was fixed in an update.
  5. I did run the PlexDBRepair tool and all seemed OK. I can dig into that a bit more, just in case. *edit* Having the repair right in the docker is slick, thank you for pointing that out. Gave that a go, but all looked good.
  6. I'm experiencing the same issues and I'm going crazy trying to figure it out. I don't see any errors in the logs and it seems completely random when it stops responding. The only errors I was able to find were: - HTTP error requesting GET https://*****.plex.direct:443/identity (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name '****.plex.direct') - Unknown metadata type: folder - Some errors related to the DVR feature and I completely disabled the Plex Tuner Service for now I have updated my wildcard cert, verified DNS settings and even bypassed my adguard home dns servers. I enabled "Strict TLS configuration" in hopes it was some old clients causing the issue. Any suggestions would be appreciated as I'm having issues troubleshooting when the logs show nothing and it doesn't crash completely (no crash dump). Thanks
  7. I am also experiencing this, but a reboot temporarily fixes the problem. I think I had some "files in use" or "mover" issues that caused it to hang?
  8. The above is not working for me. It won't even let me disable listening on 443 (HTTPS) for SABNZBD, it keeps enabling on reboot. There is really no need for me to listen via HTTPS as I use SWAG for reverse proxy. All my *arr applications talk to SABNZBD via HTTP and not HTTPS locally.
  9. It also seems as though I can't add back the TRIM plugin once I downgrade
  10. Same thing with my Nvidia card I also would like to know what to do without the Nerd Pack. Guess I'm downgrading for now
  11. Has anyone been able to reverse proxy the Roon web display? I want to do this so I can have Home Assistant display the Roon Web Display on some devices and it requires HTTPS. I have Authelia in front with two factor and allowing bypass on local network. I just get the Roon logo and the "display" doesn't show in Roon, so I think I am missing something in the Swag config
  12. Looks like changedetection.io added sharing options, but they don't work. "Could not share, something went wrong while communicating with the share server." Is there any docker env variables I need to add to get this working?
  13. pover://user@token I guess I could try email as well *Couldn't get email to work either* Both these apprise methods work in my changedetection.io instance Sabnzbd docker log: 2022-03-30 11:30:11,395 DEBG 'start-script' stderr output: 2022-03-30 11:30:11,395::INFO::[misc:1161] [N/A] Running external command: ['/usr/sbin/nice', '-n10', '/usr/sbin/ionice', '-c2', '-n4', '/usr/lib/nzbnotify/sabnzbd-notify.py', 'error', 'SABnzbd: Error', 'Notification script returned exit code 1 and output "Traceback (most recent call last):\n File "/usr/lib/nzbnotify/Notify.py", line 174, in <module>\n from nzbget import SCRIPT_MODE\nModuleNotFoundError: No module named \'nzbget\'\n"', 'pover://*****@******'] 2022-03-30 11:30:12,235 DEBG 'start-script' stderr output: 2022-03-30 11:30:12,235::ERROR::[notifier:375] Notification script returned exit code 1 and output "Traceback (most recent call last): File "/usr/lib/nzbnotify/Notify.py", line 174, in <module> from nzbget import SCRIPT_MODE ModuleNotFoundError: No module named 'nzbget' "
  14. I might sound stupid, but where is nzb-notify located in the image? install_path_nzbnotify="/usr/lib/nzbnotify" (I'm stupid) Still get "Notification script returned exit code 1 and output "Traceback (most recent call last): File "/usr/lib/nzbnotify/Notify.py", line 174, in <module> from nzbget import SCRIPT_MODE ModuleNotFoundError: No module named 'nzbget' "
  15. I followed those instructions and still get errors when executing via SAB. Docker logs show that exact error I listed above. Seems like requirements are missing, but I ran the pip install -r requirements.txt command without fail.
  16. Anyone have success getting the nzb-notify script to work? I see that SABNZBD is removing pushover support along with others in favor of nzb-notify. I get error "Notification script returned exit code 1 and output "Traceback (most recent call last): File "/config/scripts/nzb-notify/Notify.py", line 174, in <module> from nzbget import SCRIPT_MODE ModuleNotFoundError: No module named 'nzbget' "" I can console into the docker and run the script without issues
  17. I noticed that /data.json isn't being updated but instead /rollar/data.json (yes, rollar with ONE r). Not sure what is going on here
  18. Is there an easy way to edit Plex profiles without having to console into the container and edit files at /usr/lib/plexmediaserver/Resources/Profiles/Chromecast.xml and so on? Can I map this path to my appdata folder and will that prevent it from being updated when the docker container updates?
  19. Thank you, after following the migration steps above I'm back up and running. The template did throw another port mapping in there, so I had to remove the 80:3333 one and just rely on 3333:3333
  20. I'm getting key errors as well and server won't start up properly. chown: /data: No such file or directory Even though I see the APP KEY in the txt file
  21. How did you fix it? *edit* Looks like just updating to v0.9.82021 fixed it for me as well
  22. Yeah, I did the same and still can't get the webUI