dgs2001

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

Ok so I'm confused but here goes - 1-servers been running fine for months 2-flash was backed up 2 days ago 3-today i did a clean shutdown to increase the ram in the server 4-unplugged server and removed 2x16gb ddr ram sticks 5-added into same slots 2 x 32gb ram sticks 6-plugged back in switched on and hit f2 to get into bios 7-updated bios 8-rebooted expecting unraid to fire up 9-direct connected monitor didnt respond, waited for approx 1 minute 10-with no screen output and no activity lights i hard powered down 11-left server unplugged for a minute, removed additional graphics card to force on board then reconnected power 12-server started straight into uefi bios screen, no unraid 13-tried another couple of times in different usb ports- no difference 14-used usb creator to install fresh unraid trial to a second usb stick 15-installed 2nd usb and booted straight to unraid no problem 17-manually copied everything from original usb stick to desktop 18-used usb creator to put a fresh unraid on original usb 19-server boots straight to unraid from original usb stick (Fresh Install) 20-used usb creator to put 2 day old backup on 2nd usb stick 21-2nd usb stick will not boot to unraid, just goes to uefi bios 22-check with a third usb stick that a fresh install boots correctly - it does 23-use usb creator to install 2 day old backup to 3rd usb - it wont boot just goes to uefi bios screen 24-thinking maybe my 2 day old flash backup was somehow corrupted i find a 6 month old backup and install that to all 3 usb sticks to test 25-none of the 3 usb sticks will boot to unraid from the 6 month old backup (srever goes straight to uefi bios settings 26-all 3 usb sticks will boot to a fresh install I'm confused, all 3 usb sticks will happily boot a fresh install but none will boot either backup & None will boot from the original files. Can anybody help? flea2-diagnostics-20230522-1538.zipCould this be something to do with the increase in Ram ? (The server reports the ram correctly in the bios screen and all other settings look fine) The attached diagnostics file is from the original flash 'logs" folder

I used a T620 with unraid for several years and it worked well. I did have to keep it in BIOS mode in order to be able to get hardware passed through successfully but I am talking back to when we had to stub vfio devices, and i never worked out why! My suggestion would be to swap hardware without making other changes, once its back up and running then look to make any other changes you want to make.

Following the information above from Akagami I was unable to get a fresh ubuntu desktop VM logged in to NORD so I had an interesting chat with Nord this morning and they confirmed there is an issue their end which they are working on to do with MFA. Basically even though a browser window shows logged in, if you have MFA active the linux terminal returns "You are not logged in" Nord confirmed they are trying to fix this and told me i had to dissable MFA in the meantime. Not the best from an otherwise seemingly reliable provider.

Nice work, Do you fancy sharing a screenshot of your container settings (minus the private key of course) Thanks

Yes it does seem there is an upstream issue. My streaming box is also now unable to authenticate with NordVPN. I haven't tried it and its not dockerized within CA yet, but Bubuntux has suggested using the NordLynx version of the app - https://github.com/bubuntux/nordlynx And if anybody else with better docker skills than me can help, here is a link to the Nord Instructions for how to dockerise the app - Official guide to Dockerise NordVPN app

Thanks, I did just try changing password but no joy. Changed it back again but still no joy. Its all been working fine but seems to have fallen over sometime in the last 12 hours for no apparent reason. Now it wont reconnect I'm getting exactly the same login error as 'matty2k' posted. All works natively through the nord app on windows and mobile. Is anybody able to confirm what version of the app this container runs? I believe the latest is 6.41.10.0 Thanks