cammelspit

Whelp, there was data left on the old SSD but unfortunately, it didn't work copying it over. It was only a small snippet of the databases folder for MariaDB and nothing for LE or Nextcloud. All I can assume is running the dockers without their proper data somehow damaged it beyond repair. At this point, the only thing I can do really is just going on ahead and reinstall let's encrypt, MariaDB and Nextcloud again from scratch and try to be more careful next time. Still sucks that the 'proper' procedure outlined in the WIKI was not apparently enough to work properly but I guess if I was more experienced I would have caught the issue beforehand and I wouldn't have had to deal with this problem in the first place. 😢

Oh yes, I had. It had been working for months without any issues at all. My plex.domian.com cloud.domain.com all of that stuff worked fine along with the SSL certs. Nextcloud was working fine as well, I love using the auto-upload features for pics and vids I take with my phone of the family.

Er, you know... I don't think I did. Shit, maybe those missing files are still on the SSD... It's in the server still but fully disconnected since I also added two more 10TB drives to the system and they are preclearing now. The preclear will be done later today so once that happens I can maybe pull the drive out, use a USB adapter and plug it in. If the files are there I can then see about copying them over. Hmm, that might work assuming they are still there. Yeah, I think that is what I am going to do. Hope to god it fixes it. Well, I'll be sure to keep you posted but it seems I can't do anything at all in that area till tonight or perhaps even tomorrow morning. Thanks for the tip.

For example, I have this when I look at the files. From what I have read, I don't think I am supposed to have all dashes right? This means I don't have permissions to do anything with the files. I think... So it all boils down to the fact that mover somehow dropped my permissions on the files. I just need to know how to allow user nobody to be able to read and write these files again. I think I have some idea what's going on I just don't know how to fix it.

If I were to just hail mary it and make every file owned by that user, what would I do? chown? Sorry for the noob question.

@John_M Ok, I meant I did indeed set them to 'yes', mover, swap drives, set to 'prefer', mover, now it's all broken. @Squid Frankly? I have no idea... I'm still kinda sad right now tho. No idea how hard it will be to get everything just right again if I decided to just toss out my current installs of these dockers and start over. THough, following the procedure in the unraid wiki shouldn't have caused this problem I would have thought. https://wiki.unraid.net/Replace_A_Cache_Drive I just did what this said to do.

AFAIK, the two big ones that aren't working are Let's encrypt and Nextcloud. I have the original SSD but I used the procedure in the unraid manual and I set all those shares to not use the cache, shut off docker and VM engines, invoked mover, swapped the drives, reenabled the use of the cache drive and invoked mover again. So the original drive doesn't have appdata folders on it anymore. Man, what else can I do? Im pretty useless when it comes to a lot of this stuff so setting up nextcloud and let's encrypt in the first place was not by any means an easy thing for me to do and I would prefer to not have to do it all over again. Was my procedure for replacing the SSD wrong? Was there a better way to handle this?

Hey guys, I replaced my cache SSD recently and several of my dockers have stopped working. After some help from the LS.IO guys on discord, we have figured out my permissions for appdata are all messed up. I prolly did something wrong. What's the procedure to redo those permissions so that appdata is accessible normally again?

Hi! I was wondering if I could get a hand figuring out how to fix an issue I am currently having? After an update in the last couple of days, I can no longer access the web UI for my nextcloud. Before, I had the reverse proxy from your let's encrypt docker all working like a champ for several months. I know that MariaDB is also a part of how nextcloud works so I wasn't sure which if the three docker support threads I should have posted to. I'm not so good at Linux in general but from my layman understanding of the logs, it can't find the DB? Perhaps a permissions issue? I just am not skilled enough to know what to do beyond simply reinstalling and setting up everything from scratch which I would prefer to avoid. The let's encrypt log is especially concerning since it's just the same error over and over but I would still have expected nextcloud to work even if the LE docker and reverse proxy didn't. Anyways, here is my servers diagnostics when I first found out it wasn't working a couple days ago. I also JUST replaced my cache drive with a new 1TB Samsung SSD instead of an old as the hills 120GB PNY POS. Anyways, it wasn't working before the switch so I don't think that has anything to do with it. Below I have attached the logs for MariaDB, nextcloud and let's encrypt dockers as well, though the let's encrypt log was taken from AFTER the SSD swap. I really appreciate the assist, thanks in advance! connollyserver-diagnostics-20181125-0802.zip nextcloud log.txt maria log.txt letsencrypt.txt

Really? That's it? Of course, it worked... I feel silly now, I probably should have at the very least tested another browser and then when it worked I would have thought to clear the cache. I'll bet I'm not the first nor will I be the last to have problems that are fixed this exact way, right? 👍 Thanks!

Just updated unRAID to 6.6.5 from 6.5.3 and now this is what I get when trying to access the Jdownloader WebUI. Nothing was changed otherwise. I have tried deleting the container and reinstalling it, changing the port to access the UI, the same result. Any other troubleshooting I can do?

Perfect, thanks!

What you guys are saying is I can edit the name and such for the currently installed docker and then CA will allow me to add it again? Just a clarification.

So, I was wondering... Is there a way that I could easily just install a second copy of a docker that is already installed? I ask for a couple of reasons but mostly I want to set up a second Plex server on the same server and do some experimentation without completely ruining my primary Plex config if I happen to much something up. the option to install from the CA plugin is removed once you already have that docker installed. I know I will have to rename the docker and such and that's not a problem for me. Thanks!

I too had issues with rclone on the newly updated 6.6. I started a transfer to my google drive and then the 6 cores I have used for unraid itself pinged to max CPU usage and the whole of unraid became unresponsive and was effectively locked. No web GUI, nothing. I ended up having to physically login on the server and restart from the CLI. When I came back and checked plugins page there was a third tab at the top listing plugin errors with rclone. I then uninstalled it entirely, rebooted the server, installed rclone, rebooted one last time and the errors were all gone. I didn't have the mind to take snapshots of it or anything at the time and when the server was locked, I didn't have access to any of the drives or anything. So for the moment, it seems a simple uninstall and reinstall is what it takes to fix rclone on a unRAID6.6 upgrade. though, I haven't started using it yet since then so I will add to this when that happens.

Holy hell in a handbasket Batman! I now feel rather silly and I think you kindly for pointing out my silly syntax mistake! ?

Hi! I am trying to access my gdrive from this plugin and I am using spaceinvader's video as a rough guide. I am getting issues listing the directories as a test to make sure everything works. rclone lsd google 2018/08/27 12:01:50 ERROR : : error listing: directory not found 2018/08/27 12:01:50 Failed to lsd: directory not found I set the remote to have access to everything during setup, I believe this was option 1 at the point. Is this an issue with the plugin or the version the plugin is using or something with rclone itself. If this isn't the plugins fault, and to this point I am not sure, it would still be nice to get a quick hand figuring out what I am doing wrong. If I explicitly set a directory such as rclone ls google:Client Data Backup It does work and it lists the files as expected but I can't seem to LS or LSD the root. Should I try using the beta plugin instead? I may just be stupid here or I may be wasting your time with problems that I shouldn't be bringing to you but I am super new to Linux in general and this is my first time ever using rclone so I am not sure if the problem is me or not. If it is me then you can please just tell me to take a hike and I will, I promise. ?

I have booted into GUI mode once before for troubleshooting so I know this configuration should be working. I haven't done any upgrades to hardware or unRaid itself since then but now when I tried to boot into the unRaid GUI, all I get is a blank black screen on the server machine itself. Any ideas?

Done, thanks again! ?

Surely, not as much as I do! Thanks again all of you for the assist! EDIT: I actually get a 404 when hitting the donate button.

AAAAHHHH! I FIXED IT!!! WOOO! Alright, sorry, I'm so happy I could literally start running around in circles right now! So, here's what I did. After remembering I use the 'docker network create proxynet' command, I opened the terminal and tried just using 'docker network remove proxynet' but it errored and told me that it had active endpoints. I then recalled I could disable the 'preserver user-defined networks'. I disabled this in the docker settings of unRaid and then after re-enabling the Docker engine, I was finally able to remove this virbr0 entirely. From there, I just opened the Plex WebGUI like always and it instantly showed me the create new server stuff. Hell yes... Honestly, guys, I can not put into words how incredibly frustrating this has been for me over the last two days or so. I have also never gotten as good support before from such a knowledgeable group of people. With the powers of all of you together and a little bouncing of ideas off each other, we have fixed it. Where can I donate to the linuxserver.io? ???

The difference here is this virbr0 I made myself from the command line as part of the tutorial. I should be able to remove this specific network, shouldn't I? It is not part of the docker stuff by default.

I think you are on to something. First off, I originally set up this docker when the server was on the 10.10.10.0/24 subnet, same as my current machine so that's prolly why it worked. And with what @ijuarez and @Hoopster said, it seems that it is binding to some subnet with 192.168. subnet. Ok, so I was following Spaceinvader Ones's tut on nextcloud. In his tutorial, he has you make a new network, low and behold it is set to a 192.168. subnet! So this tells me plex is binding to Vibr0. I have since moved the server back to the 10.10.10.99/24 subnet so that shouldn't be an issue right now. However, in unraid, I can't use the GUI to remove virbr0 route. My issue now is I simply don't know the commands to remove it entirely. I decided after the fact that I didn't want to have any of my docker going through virbr0 since it made them inaccessible locally due to the way my network was set up. I COMPLTELY forgot about this too as I am not using it and sort of haven't thought about it in a bit. I would be willing to put money on this being the problem. Does someone know the commends to remove this virtual network?

Since you mentioned it is trying to use a subnet I simply am not using, is there a way to manually force Plex to use the subnet I am actually using? Would there be any kind of reason why it would be trying to force the wrong subnet in the first place?

I will do it right now and report back! EDIT: After backing up and deleting the docker.img and reinstalling the plex docker, same results. What I don't understand is how this is even possible? When I delete the /appdata/plex folder and have a brand new docker.img it should be as if Plex had never ever been installed in the first place... I simply don't understand how this is possible at all. It should be exactly as if I were starting up for the first time and allow me to setup a new server. ?