PhilDG

Thank you for the advice - I'm rebuilding parity and will probably swap the drive connections sooner rather than later

Hi, I just logged to my server to see a message that my parity disk is in error and has been disabled - it shows a red cross against the drive and a '1' in the errors column Can someone take a look at my diagnostics please? Not sure if I need to get ordering a replacement or if it's just one of those things that happen and a restart would work Thanks so much in advance tower-diagnostics-20230719-2125.zip

Thanks for your quick reply - there was an update available to me which I have installed - will keep an eye when my next parity check starts Thanks again for your help

Hi, like some others here, my log file is getting filled with the following every 6 minutes during a scheduled parity check - I couldn't see if there is an answer to this as yet

Not sure if it's a problem my end but I had Overseer working great. This morning there was an update for the docker which I applied and I can no longer connect - I'm getting 'This site cannot be reached xx.xx.xx.xx refused to connect. I'm using the default settings for the docker - not sure what other information to give

Hi, How do I update the server version. My client is saying server version 1.3.0.0 or higher required. When I load the page on my PC, it says that the new version (1.13.4.5251) is available - how do I update this? I have tried restarting the docker.

I'm no longer getting any updates from iplayer. It looks like the last download I had was from 20th October. Looking at GitHub it appears there is a new version of the get-iplayer. Does the docker automatically get this?

Brilliant stuff - thanks for that - fixed now (and when I actually read what you'd put!! - Note to self -read it properly)

I'm suddenly getting an issue with this container. Had an orphaned docker image so I removed and tried to re-create it. Pulled all of data down but then got this message at the bottom of the screen: Unable to find image 'the:latest' locally Pulling repository the Error: image library/the:latest not found I upgraded unraid to 6.1.9 yesterday but this docker container appeared OK.

I do use chrome - didn't realise it was an issue - am back to normal now thanks

All of a sudden, I'm now getting the message that crashplan cannot connect to the backup engine this morning. I have tried re-starting the docker, and then tried to force an update. Crashplan is at 4.6 and looking at the website, the engine is connecting to the cloud and backup up. Does anyone know if the engine version has changed again as this is often the issue - my desktop version is running 4.6 locally and connects to it's backup engine - it's just using novnc that cannot connect. Cancel that - I restarted the server and we're back in action

I spent hours yesterday trying to get this working - wasn't until I re-read the post by sacretagent which was to keep manually restarting the crashplan docker and check the log files until you have the same version on the back-end as the front. Finally I am up and running - thank-you sacretagent - just waiting for the gui to be updated but at least we're backing up!