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

Yes same here, The log is showing Incorrect User or Password. I dont know how the container is authenticating, but its possible this is a change at the nord end.

Ok, As far as I am able to check this container is working with the NordLynx (NordVPN custom wireguard) protocol on my set up. I am able to route several docker containers through this container by changing their container settings as follows - eg NZBget firstly switch to advanced view then Network Type - None add the following to Extra Perameters --net=container:nordvpn Save this and then add an additional port within your nordvpn container Once completed you will need to use the local server URL:port to access the other docker web gui EG - NZBget could be accessed at 192.168.1.1:6789 if your server is local ip address 192.168.1.1 I'm no expert at this but to check what ip address your containers are connecting to open a NordVPN docker Console (Terminal) window by left clicking the Nord icon and selecting console. Type the following curl ifconfig.me The response should be a different IP address to that of your main server terminal window, you can also check other containers, but NZBget does not have Curl installed so it wont show in NZBget console. Hopefully that all makes sense, but if not search up more spaceinvader videos and also this old reddit thread may be worth a read Reddit: Passing dockers through a vpn container

Hi TechMed, sorry you have confused me a little! Are you trying to route various docker images through either NordVPN or PIA? or are you attempting to remote into your Unraid server through a vpn tunnel ? If as I suspect you are looking to tunnel into your Unraid server GUI then you should perhaps be looking at the wireguard service built into unraid. This allows you to create a tunnel from your remote location to your sever gui login page withoput the use of a paid service like nord or pia. The same functionality can be achieved with the my servers plugin from Unraid. This thread as far as I understood was more about using one container to connect to a vpn service; then routing other dockers through the vpn docker which allows many docker containers to connect to the net through the vpn docker. NordVPN offers both openvpn and nordlynx protocols, with most people finding nordlynx to be a faster connection. This NordVPN container allows the user to choose between the two protocols. Hopefully that makes sense

All Working on NordLynx here. Thanks for a fab docker. So to recap for those with issues- 1- check network setting in the nordvpn template, you need to click 'show more settings' to see this and remember if you access your router settings page on 192.168.100.1 then your network setting would be 192.168.100.0/24 (google CIDR notation for more) 2- check your nord access credentials, its easy to mistype a username or password. 3- add the nzbGET port as an additional port to nordvpn docker. If using the default port 6789 with nzbget then add to nordvpn Config Type : Port Name : nzbGET Container Port : 6789 Host Port : 6789 Connection Type : TCP Description : nzbget port 4- The only setting to change on the nzbGET docker config page is the network, if nzbget worked before then just change the network settings. To do this, select Advanced View, select 'None' for network type and add only the following text to Extra Parameters '--net=container:nordvpn' 4- Start the Nord Docker, there is no web gui but to check its working click its icon and click console then type curl ifconfig.io this should return an ip address, it should be different to your host machine ip - google whats my ip to verify. 5- start or restart nzbGET 6- type your unraid server LAN IP address : 6789 into the address bar ie. 192.168.100.100:6789 7- hopefully you are now seeing the nzbget web gui Well it works for me so sorry if this is confusing or it still doesnt work

If you end up with an LG1200 board as I did, make sure you choose one with good pcie coverage. many of the newer boards have m.2 slots but if you use them this dissables onboard sata connections. I made the mistake of grabbing a cheap Z490 msi motherboard. Its a great board but only has two full size pcie slots and 2 x m.2 slots and once the m.2 slots are in use some of the six onboard sata connections are dissabled. I think Im going to end up having to change it for a larger e-atx sized board which will have better conenctivity. It depends what your aiming for. I was using a repurposed dell T620 tower server with two x e52690 cpu's and 128gb ram. It coped with alot and never let me down, running file storage for a small company and many dockers and vm's too. A change of job has meant building new and wanting to future proof the setup and being a cheapskate I went amazon warehouse LGA1200 with an 11th gen i91100 both used but fully functional. All just seems a little leaner and smoother than the old hardware, but its impossible to know if that's just my perception.

Thanks Squid, your correct. Using an alternate browser the text displays correctly. I was using Firefox when i noticed the problem, but Edge (Chrome based) does not have the same issue and neither does Chrome. Interesting as its not something I remember from before I upgraded from 6.8.3 to 6.9.1 - makes me wonder if I'm just getting old 🤔

Strange one, Can anybody help me uncover why my terminal window is not displaying text properly. The picture shows how text displays whenever I open a terminal window, this also remains after a reboot. As you can see the right hand side of the letters is simply not showing

I had not realised this was already a thing in 'FCP' for Unraid 6.9 As ever great responses from the community. Thanks

Hi All, Not sure if this has been requested before and also not sure how easy it would be to implement, but I just think it would be a great shortcut if notifications were clickable. for example; I get quite a few niotifications from the 'Fix common problems' plugin. They always suggest I investigate at 'Settings / User Utilities / fix common problems' I feel It would be so intuitive to have these notifications clickable to take us straight to 'Fix Common Problems' or which ever area the notification is pointing us to.

pm1961 did you get this sorted? One thing I have noticed previously with swag / docker / unraid / duckdns / cloudflare / pfsense ... etc When making changes or getting things set up it takes time for dns changes to propogate throught the various interfaces etc. I have countless times been looking for problems that simply dissapear when all the networkimng interfaces catch up with themselves. Nowadays as somebody who tinkers if I am changing things to do with or that require dns and forwarding I tend to reboot my pfsense box and my pc before checking whether things are working. I am sure there are commands that will release and renew leases and dns but i just find its simpler to reboot and then I know its not a cached dns problem. dgs2001