rbmatt1s

I'm reasonably tech savvy, but I can't get the docker container to install with tailscale set to yes. With tailscale off, I was able to get it up and running, but it was very difficult w/o reverse proxy. I had to ssh into the machine and pretend to be localhost. I would prefer if I could just access it via tailscale like everything else

Awesome, thanks a ton MAM59

I read that 2.5G networking has been a mixed bag, but I went for it anyway. I bought the TRENDnet 2.5GBase-T PCIe Network Adapter, TEG-25GECTX which uses the Realtek 8125 chipset. I installed it, then switched the interface rules to put "r8169" as eth0, turned it off, moved the cat7 cable to the 2.5G port, booted up and everything just worked. Now my question is, I set "Desired MTU: 9000" but I don't know if that was wise, I get one Jumbo Frame warning in Fix Common Problems. Any thoughts?

i think it's working again.

1) I set appdata, backups, system, and Transcode to "Prefer:Cache" 2) I am running mover 3) when mover finishes, the appdata folder should be full of the app data from disk3. So at that point, I just go to "Apps"->"Previous Apps"->"Select All on Page"->"install 13 selected applications." (I don't need to run Restore Appdata because the appdata that mover moves over is already the most current appdata, I didn't lose the app data and have to recreate it from the backup tar.gz.) Then after I install the 13 selected applications, just reboot the server and I should see all the apps in the Docker tab, yes?

Okay, I'm paddling back to shore. I got the Cache Drives functioning. Mover is moving the contents back to the cache drives. When mover is complete, do I need to recreate the docker image, run CA restore v2, or copy the appdatabackup folder or some combo?

How do I get the cache drives not disabled?

okay, so i ran the restore feature, but it didn't work, now I see this: Docker still shows this What should I try next?

okay i think it's restoring.

I have the appdata and appdata backups, but how do i restore them?

Hi, i'm running UNRAID 6.11.5. I had 2 250 GB SSDs in my Cache pool and they were consistently filling up. So I followed this procedure: I replaced the drives with 2 1TB SSDs, formatted them, adjusted the shares to use the cache, then ran mover. When I went to turn the docker containers back on, they were gone, and I realize I made a fatal mistake. I missed step 3 in the initial protocol: "Settings -> Docker: disable Docker and click apply" What should I do to undo the damage I've done, rebuilding every docker container from scratch would be very painful. I have the two 250 GB cache drives sitting next to the machine right now. I could reinstall them, but I would like advice before I make matters any worse.

Very odd. After a while it started working. Is there some kind of invisible process where for the first, I don't know, hour, on the backend the Resilio Sync client needs to download a .torrent file so there is something happening that is simply invisible to the users and myself?

I got the container installed, it seems to be fully operational, I shared a folder, it seems to be sharing the folder, but when my peers click they link, they just get... the folder without any of the contents. Resilio can see the files, because when I added the folder it spent about 10 minutes indexing about 25 gb of files. Could be a port thing? I forwarded the listening port on the router to my UNRAID. Would love some ideas.

I added the extra param and that fixed everything. thanks Mr. Squid.

yep, maybe the container size button in Unraid is wrong?

I should mention that I went into /config/logs and nuked the log files there. Still shows up in the Unraid GUI as 10gb Sent from my Pixel using Tapatalk

Sorry for this pedestrian issue but my Unraid flashed a warning: Warning [TOWER] - Docker image disk utilization of 76% I looked into container size, Sabnzbd has a 10gb log file. Any idea why it's gotten so large, I thought that sabnzbd automatically kept logs to 5MB. ideas?

This is great! I was pulling my hair out and you solved it in about 5 minutes! Bravo!