Per-Arne

If you changed the parameter "Password Access" to false it means that password authentication is then disabled. If you then try to connect with a client that doesn't use a certificate to authenticate then you will get the "no authentication method" error. If using putty to connect you need to setup putty to use the private key when connecting and also if you used a password to protect the certificates with (entered during creation) you need to enter the same password to putty, if not then putty will not be able to use the certificate. Good luck.

Hi. I have managed to get certificate based authentication working. The client that is supposed to connect shall use the private key not the public key.

Hi, I have been using this docker on unRAID for a while now. I intended to install a second instance of the docker but when searching for it in the APP section I can't find it. It seems as if this docker has been removed from the unRAID repository? Is it removed or have I made some error? And if it's removed then why? Regards

Hi! Last night I run the 'update OS' feature and I went from 6.6.7 (I think) to 6.7. Everything went OK, I restarted my server which never came back again. When I now have restarted it in 'GUI' mode there seems to be no ethernet interface anymore. I can not ping it, neater can I reach the Web GUI. If I run a if config from the GUI on the server (using a monitor) I only get two interfaces. br0 and lo. Does anyone know how I shall proceed to rectify this error... Regards Per-Arne Update: Crap, I just found this topic: I'll see if I can get some pointers from in there.

Maybe i was to quick here, after what seems to be a couple of reboots it seem to be ok again! Ill keep my fingers crossed and check tomorrow again! Thanks alot for quick support!

Hi! Yes the docker is running when I restart the server, but Im still not able to start or stop the docker service. Well to be correct, i can stop it but not start it. Unless i restart the unRAID server. /Per-Arne

Hi all, I have messed it up (again)! To make a long story short I have been struggling with large docker image for a while now and in my quest for why my docker image allocated 40GB I in frustration played with the docker system purge command. OPS!! I should not have done that. All I could se was this: root@unMINI:/var/lib/docker# docker system prune WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all dangling images - all build cache Are you sure you want to continue? [y/N] y Deleted Networks: br0 Total reclaimed space: 0B root@unMINI:/var/lib/docker# docker system prune -a WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all images without at least one container associated to them - all build cache Are you sure you want to continue? [y/N] y Total reclaimed space: 0B root@unMINI:/var/lib/docker# docker system prune -a --volumes WARNING! This will remove: - all stopped containers - all networks not used by at least one container - all volumes not used by at least one container - all images without at least one container associated to them - all build cache Are you sure you want to continue? [y/N] y Deleted Volumes: 08520a7e2dc86118ff5799e71333484a3b8e70907413d7561c31fb2ae1c17847 34934e7df00ee377b966b14345a9663728a492a016f22849d2d51c233cd9ce44 e2221e47fed82145896d9837ddf19c24ae65c333f354570b181e39a78868ca09 f8cebfd6b9dd5a8e05b77f2f4b0b4f44a8b2539e7bdaf368bdaaa3180f517796 e19220edc1e7cf18416f1aa6a725784e058eb00e1d080f458ec98e0c01e2347d 02a3b04d526a5269f01e45e28c4514e8c482f30c9572e3dfece353f8611f313c 630fac242033c1162798d264f283c476152e06a84ba22a17cb8bf609a394ef65 85df6ee42cbf256af7de0aac71564c22a9a89d091f220e51e18391b7485f397e ab1aaf7460693709e0730dbac771731e9c5edbe5715bde6ee74cc3e78ad5207b b18e9c45306ceb00e8fdbe55ac35717bf47e15257166d93ba7e9ad9abd9a12d6 a82b8e0276977a59265298a99b675c0ec2462ceb7e6f09208a189714b0c75b12 0750a5f8cfbdff419a9edae5d9a8fd62864572fbc39ec63aa0aede31fae5032a 0951881a9f713c59c84b898a4949be15ee52bc06815464649343c5e457545576 2c445d6f2637fe14542c0ffb29550c2feff892331dd64610c1924ff9bfa00820 4ee62fa931385a6d9423f4df81e0b145375a6e2478f775789c74685f366f827e 632f0663815ef554c78543d52dbd763ec18c4d6a7a7ca911cb3ab3e50066ab0e 3ea7d30058cc0c480be03b86856ac10674f6834319c458537f121b67b231d27a 5a02d8b4f5681c1d8acc459a90af9c1b7db7f020edc98732a6846aa11bcd3b1d 98abde9158b51c7a7b3a3c6ed05f6d32387771c39cd6af0d8126032e1bbd410b d8783383f9f5e97b5b1ae77f1041a6741d47ddbec1a1f37415f40499d614e759 1e7c4d7e820bfb62ba9e0b0855901e2ab91dd406fc3c545b23de9fc3c7633902 24c6c7c3bea677b67f49b34314acaae13b8b699bade6af39fece56f64c7b9406 72ea8d956b640803a91a5d3d9d4d3c0fff2de1e91337db53569a0178d3ffcf4c 7ee420efdfd2a02236bb8718760a3177e54897f4033c077adbb934f72f213350 dd570e85241b8e6ae00ce7830dacf133a008944fceaf1701c75a9a0d18e81125 3fd37830974e47776764bd3883ab2869ed24a033c6e26863afe41d5c5886a36f af2becd67f38c4648943df08ea83da253f85f344b6f9ca185828ceb3b6662b49 c4c0f54707cf282a28677f7120f4065faf21c0024b026109d1d90d38d0726e55 dc67fbe8e9629e77917b839b91e376189a72d3043a32c725861aa2a33f2e9c56 0d324c4bd1551a7db9aa130b353d355ba608b2ae1917be67e51deca390e79359 9eb06359499c7f74d7d5ef3ff874be2f37235260af5d0d0dfcfd5eda944c4835 dc048262ea4506aaf6724bc070f88e1762407719c0e6aedb96eb51ff46912219 4271e7aecfa27531733d990561a9f86108fb702690ddc9232aee704dce12ca48 ea9f6a625b3d444a6e44b8da50388e4b4b0ff42e94c0636c18154c3050858c74 Total reclaimed space: 133.8kB Which tells me that I removed network br0? After this I can not find the Docker tab in the menu bar in unRAID. Neither can I start/stop the docker service in Settings/Docker. Does anyone know how to remedy this issue? /Per-Arne