don256us

CA Cleanup Appdata for the win. I installed this plugin, removed Plex with image again. Ran CA Cleanup Appdata to remove all unused containers. It failed to remove Plex but it gave Plex as an option for a second run and... after a short moment that felt like forever, it finished. I reinstalled Plex and it's working. Gotta rebuild my db but a small price to pay. Thank you Arbadacarba for helping. It's appreciated.

I just had a coworker suggest Cleanup Appdata docker to remove this data. I will give that a run tonight and see what I get.

It is set to Host. Note too that everything else works. I can get to all shares and my other docker is working. I input my local IP 192.168.1.9:32400 If I input the port number for my other docker, it works perfect. Plex worked too until just recently. The issue is NOT connected to any updates as none were done from when it did work until now. I did look for updates as part of my troubleshooting but none were available.

I've been searching around here and other sites trying to find an answer that I understand. My Plex server (docker) will not... serve. Not even locally. I have UNRAID ver 6.11.5 PLEX (Official) was working up until I had an unintended power disconnect on my UNRAID server. Plex did not come back. It would seem to be fine except that it will not communicate... at all. If I go to the docker and click on the web UI, I get a "failed to connect" or "Refused to connect" via Firefox and chrome respectively. Not only can I not view my media, I can't get into any settings that the web UI may present. I've "Removed" the docker and reinstalled. I "Removed" the docker *and* the image file then reinstalled. No love. I see that the folder with all of it's settings remains in appdata even after uninstalling. I tried to do a more complete uninstall but I am unable to find how to delete EVERYTHING Plex *or* how to force the Plex container to reinstall from scratch. Note: Other docker containers work perfect. E.G. Folding @ Home will display the web UI no problem. I've spent a few hours looking for better answers from different avenues of attack but nothing has be helpful to date. I'm not good with linux so please be kind. I'm not a computer idiot, just a linux idiot.

That worked. Thank you very much. Now on to the next issue. One of my HDDs did not survive. It died when I lost the MB aparently. It was half expected. I'll do my Google-Fu and if I can't get it, I know where to ask. Thank you again. Oh. I will reserve the IP via DHCP reservation going forward.

I'm running UnRAID 6.9.2 My old MB died. I bought a used MB and CPU. I was able to switch all of my hardware to the new machine and things looked like it was going to work fine. For a time, I was only able to connect via local host on the physical machine. Note: I am running UnRAID on bare metal and not as a VM or docker or anything. Straight from the USB drive. I had issues with my static IP which took me a while to find and correct. I have removed the static reservation from my network. Now when I boot up, I get the Firefox browser telling me that it cannot connect to the localhost. Google seaching has not helped. I have tired different USB ports and all have the behavior. I tried different network ports on my switch. I was able to add a different NIC and that did not help. I've modified the network.cfg many times but am currently running with this: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0 eth1" BRNICS[0]="bond0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.9" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" DNS_SERVER1="192.168.1.1" USE_DHCP6[0]="no" DHCP6_KEEPRESOLV="no" SYSNICS="1" I've tried turning DHCP on then off on various tries. I have turned off IPv6. I've not messed with any of the other config files. I am able to get into the UEFI and make any changes I want and I get good picture during boot and even in the GUI. The hardware seems to work fine. Using a Gigabyte GA-X58A-UD3R (rev. 1.0) with newest firmware and a Xeon W3690 and 24 GB DDR3 RAM.