Squid

Because there's no password set. Try it again.

You want to do the 6.10 upgrade

It looks like the network stats plugin automatically tries to download the package on every boot, instead of saving it to the flash drive. In your case, the network isn't completely up at that time and it fails. Ignore the error (it's harmless), Uninstall and reinstall network stats. And post in the support thread

Set a password in the local GUI?

It crashed. First thing to do would be to run memtest from the boot menu for a minimum of a pass or two

Delete the /media mapping and add in /tv /movies Mappings for media don't mean anything at all and can be changed at will for the most part.

You should probably drop Seafile an email, as that version (last updated 3 years ago) is what they themselves have published on docker.

Differences between linuxserver and binhex stuff is mainly under the hood, but the apps contained are for the most part identical and indistinguishable. It's simply 2 different methodologies and philosophies on how to build a container.

If it's a virgin install with no plugins, then it would look to be hardware. Try connecting the case's reset switch to be on the power header (and leave the power switch disconnected)

I would hold off on developing this any further until such time as 6.10-rc3 is released. Major changes coming to browse.page

Known issue. Should be fixed next release

Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: off (auto) Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes Looks like the system is using eth1 which is connected @ 100Mb/s Disconnecting the cable will probably fix you right up.

Not exactly. You have to rebuild because a write to it failed. My opinion. The drive was red-balled because a write to it failed. Therefore the contents of that drive aren't in sync with what the parity system reflects, and not rebuilding it due to the failed write will definitely have some corruption. Whether this is noticed or not in unknown.

Yeah, a reboot would fix you up temporarily, but you're going to have to clear up some space on the cache drive and ultimately recreate the docker image file. As an aside, I'm not a fan of using BTRFS on cache pools with only a single device in the pool if you have no intention of making it a multidevice pool. XFS behaves far far better in these situations.

exactly

Try a different output (if possible) from the motherboard.

Do you have a cache drive? On which disks does the domains share exist (calculate on the shares tab)

Yes, but easier way is https://forums.unraid.net/topic/51703-vm-faq/#comment-557606 If all the files within any given share only exist on the cache drive, then there is no difference speed wise between /mnt/user/... and /mnt/cache/... (the system is smart enough to bypass fuse in that circumstance)

Running any user scripts that would do that? Did you build a custom kernel with the Kernel Helper? Try it in safe mode...

You've got a weird setting in docker settings DOCKER_CUSTOM_NETWORKS="eth1 " Probably from when you disabled the onboard NIC Have you tried setting static DNS addresses in Settings - Network Settings>? (208.67.222.222 / 208.67.220.220)

You've been logging in from one computer Dec 26 14:21:24 Poseidon webGUI: Successful login user root from 192.168.1.167 What is this entry? Dec 27 13:51:37 Poseidon webGUI: Successful login user root from 172.27.24.2

Delete /config/network.cfg on the flash drive and reboot. See if this continues.

Post your diagnostics

Yeah, Apps - Settings - Enable install 2nd Instance Apps - Installed Apps, Sabnzbd - Actions - Install 2nd Instance

What does this line in Settings - Docker (Advanced View with the Service Stopped) look like?