dgs2001

Upgraded from 7.14 to 7.2 Ive got three dockers (out of many) causing a SERVER ERROR when they try and start Tdarr Node (Main Tdarr running fine) LSIO - Emby ICH777 - Jellyfin maybe something to do with nvidia runtime. Otherwise all good. Thanks

Definatley something strange happening. Today my server is pretending to be a time machine. The clock shows 8:49 am Tue 27 May 2025 BST and the Parity widget shows 'Last cherck completed Tue 27 May 2025 4:54 AM (today) Duration 15 Hours, 25 minutes, 7 seconds. so an unshceduled Parity check has run and completed in the future......

Hmm thanks. It made no sense to me either !! I will investigate some more and see if i can work out whats happening.

Hi All, I have a debain VM with a share passed through. the share is a standard public exported share. This is normally accessible and the vm user has read write access, but when a parity check starts unraid seems to alter the share permissions and the vm user no longer has permission to write files. What is the correct way to set this up to make sure the debian vm user always has full access to the share? currently i am manually running these commands on the vm whenever unraid does a parity check. (the vm user is a sudo member of users. sudo chown -R nobody:users /mnt sudo find /mnt -type f -exec chmod 775 {} \; sudo find /mnt -type d -exec chmod 777 {} \; Thanks

thanks tried a restart of the docker service, but no change. that IP is my LAN, the server and my whole network is IPV4 with IPV6 dissabled. The dockers (sonarr, Radarr and prowlarr) are on the same machine, but prowlarr is routed through a vpn contaioner which I'm starting to suspect is the problem. its Nordlynx and is showing a status of unhealthy, although its still connecting according to the logs. Im going to downgrade to 6.12.13 which should help me isolate when the problem started and if it was during the change to 6.12.14

Hi Ich777, Ive been using your Sonarr container for a long time now but since the recent unraid update it seems my sonarr cannot communicate with Prowlarr, I get this error - Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [500:InternalServerError] [GET] at [http://192.168.100.15:9696/3/api?t=caps&apikey=dbcf8b***************** Same with the Radarr container too, which reports Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request. Are you able to help with this? or is it an unraid update thing. Thanks

Hi Binhex, I have been running this image of NZBGET for around a month now but am seeing lots of unpack stalls. Also seeing tls errors. its strange because the old image which was ich777 does not suffer from either problem. just keeps nagging me aboput being depreciated! Have you managed to have a look at any fixes for the unpack issue? Thanks

So stopping and restarting the docker service did not fix this, but a server restart has corrected it. Just wondering if I can get the two nzbget dockers to play nice (They are named differently and using different port allocations)

Hi Binhex Thanks for your great templates, you and other dev's make Unraid what it is. I've been using the ich777 nzbget image however this is marked as depreciated so I thought I would spin up yours and transition to the more up to date version. Not sure why or whether its the template or some strange Docker behaviour but after installing your nzbget app from the app store the settings for the other (ich777) docker have been altered. steps to recreate - install and set up Ich777 nzbget running default port 6789 click on the nzbget icon and "WEBGUI" a new tab opens correctly to localhost:6789 (yay all good) stop nzbget docker install from apps tab "Binhex-nzbget" with following change from default stipulate a different port other than 6789 (taken by Ich777 nzbget) within the template options. I used port 6799 stipulate a different directory for data to download to start binhex-nzbget open webgui which correctly opens localhost:6799 stop binhex-nzbget remove the app and files restart ich777 nzbget attempt to open ich777 nzbget WEBGUI web gui cannot be reached check nzbget logs - all appears normal and running fine. check ip address which cannot be reached and Ich777 nzbget is now attempting to open localhost:6799 instead of localhost:6789 double check template for ich777 nzbget and it is still showing 6789 restart docker service same incorrect mapping still occurs. Also if running both nzbget instances at the same time, the ich777 nzbget instance incorrectly shows the 6799 port mapping on the docker dashboard. Finally typing the correct ip and port into the address bar (localhost:6789) correctly brings up the ich777 nzbget app Hope that all makes sense. Thanks

Anybody seeing stuttering playback especially after seeking with the recent update to this otherwise excellent container? Thanks

Thanks JorgeB. This is happening with no GUI windows open. I haven't tried in safe mode though. What will this show? Thanks

Hi all, Can anybody please point me towards the cause of the syslog filling up on my unraid server? Thanks diagnostics-20231230-1530.zip

Hoping somebody can help with this one (full disclosure maybe nothing to do with unraid/FCP) - Unraid 6.12.4 All working fine and no errors from FCP Changed from standard broadband modem running in PPPoE mode to full fibre modem running in DHCP mode. Firewall / router is hardware pfsense - changed pfsense from PPPoE connection to DHCP connection. Internet Wan and Lan all appear normal. Unraid server appears normal with apps able to update and install from apps tab etc. but FCP showing the following - "Unable to communicate with GitHub.com - Reset your modem / router or try again later, or set your to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address)." tried ping -c 3 github.com but that gets this response ping: github.com: Name or service not known Nothing has changed within pfsense and other computers on the LAN can still ping github.com Help appreciated *********************************************************************************************** EDIT: So this has resolved itself. Having looked no further but left everything alone for a couple of hours all is working again and a rescan with FCP now shows no errors.

So a fresh install with the original config copied over seems to be booting and working fine. There's quite a few files no longer on the flash drive but I'm thinking that's a good thing, just need to see if anything doesn't work now Thanks

Only by looking in the bios to check it shows up and then booting to a fresh install