kal

Still getting this unfort... Im gonna switch over to Medusa methinks

Same question here. Anyone have some tips? Thanks! Give the user rw access chmod 666 configuration.yaml for example

Ive done something similar recently What I did, was remove the failing disk entirely - copied everything off it, removed it from the array (via 'new config', and a parity rebuild), and then physically remove and dump the disk. Means Ive free'd up a slot I can preclear in, and as the disk Im going to preclear is so much bigger then what was in the slot, Ive the option of replacing one of the other disks with it, for a net gain in HD space - and freeing up yet another slot (for future preclears).

dont bother this this section myself as a result - just assume its all US stuff

this is my main interest in dual parity - fingers crossed

not much help, but I had a 2tb drive fail on me also (wd green), replaced with a 3tb drive (wd red), and it rebuilt in ~12hrs (iirc)

great to see the fail2ban addition! have been investigating it myself, so imagine my delight at reading the patch notes many thanks

made the change from apache to nginx for this, and its working great nice job!

I just stop my apache instance, and run the following on my server: docker run -it --rm -p 443:443 -p 80:80 --name letsencrypt \ -v "/mnt/cache/.custom/apache/config/letsencrypt/etc:/etc/letsencrypt" \ -v "/mnt/cache/.custom/apache/config/letsencrypt/lib:/var/lib/letsencrypt" \ quay.io/letsencrypt/letsencrypt:latest auth prompts for domain name(s) and a contact email address, and then generates certs etc it works, but I suppose one built into an existing apache docker would be more ideal (preferred by letsencrypt too I believe). It could automatically renew as needed etc Your one sounds ideal aptalca, but Ive not used nginx before, and have apache working pretty well at the mo. Maybe once I get a bit of time, I might try a changeover

Don't want to come across wrong, but this is more of a general getting started with couch potato request, rather then a specific docker q? Sounds like you have the dockers running, so should be a case of following a generic cp guide at this stage

so, eh, it looks like its a browser issue..! no matter the username combo, it just doesnt work with my Chrome V43 (latest) browser (returns Invalid Credentials). Dont know if its something unique to me, but seems to work 100% with Internet Explorer 11

Tried a number of things, and still no joy Wiped, and started from scratch (inc clearing down db and config dirs) Have changed password for root - verified by trying to run the mysql_secure_installation multiple times, so password is being changed (just set to 'password' currently). Just any and all log in attempts to the web page result in 'invalid credentials' bit of a puzzler! especially since no one else seems to be having these difficulties - would have thought docker would have us all on the same playing field (for better or worse)

yea, I thought it would be something straight forward, but root and no password aint working for me for whatever reason - just comes back with 'Invalid Credentials' Changed the password for 'root' via the mysql_secure_installation command there (which did take blank as the password..), and still no joy Dunno whats up.. I have another MariaDB docker running, which was using 3306, so your one I set to use 3307. As a test, I stopped them both, and just started yours with the default 3306 (and 8080 for the web access), and no change unfortunately Wiped it and starting from scratch - will let you know how I get on

whats the username/password for mariadb web interface?

Followed the wiki upgrade process - couple of unexpected results (all good in the end though! just fyi): Coming from 5.0.5 I wanted to retain my config (disks, shares etc), so copied over config files from the backup v5 ./config. Says not to bring over any plugin data, and wasnt entirely sure what counted as plugin data, and what didnt, so just copied over the obvious config files (network, share, users etc (sorry going from memory)) I didnt copy over the go file, and didnt copy over one or two files without an extension ('core' being one of them) - didnt know what they were, so err'd on the side of caution.. Start up server, and it boots up ok, but none of my disks are assigned - 24 slots, with nothing showing (am only on a plus license, so a bit confused bout that.. still am a bit hah.. Presume the array just wont start if I try with more slots assigned then Im licensed for?) Bit nervous at this stage.. no slots assigned.. but just assigned them from saved screenshots, and all seemed fine. Not sure why the disks werent detected? Maybe I missed a file from ./config? Start array, checking box to trust the parity - array starts no problem, but parity check starts anyway..? Thought the check box would avoid that (?). I stopped it while I went over the changes, and its running one now - 0 parity corrections after 10hrs, last I looked, so all good My main worry was dropping the plugins, mysql in particular.. installed a MariaDB docker, pointed its db directory to a backup of the mysql dir and it just works - 100%. Permissions, everything! Very pleased.. particularly as I'd no idea how I'd be able to interact with the sql command line inside the docker.. will need to though, as I want to configure scheduled backups anyway, thanks again all, despite what the above wall of text would have you believe, it went very very smoothly