Squid

The hard drives would be fine. But, if you are using a cheap Android box, then while they do say "Yes I can handle x265 and 4K" bear in mind that they're lying. Not exactly lying but massively stretching the truth. They can handle it if the file sizes are very small (couple gig for a movie) Any reasonable excellent quality x265 (25Gig+) and a cheap box will choke. There's a reason why Shields cost more.

Settings - Docker - Stop the Service Delete the image (there's a check box) Re-enable the service Apps - Previous Apps, check off whatever you want and hit install

If you're asking about one of my ex GF 30 years ago, then she was definitely not "slow", but fast and always ready to go. Otherwise I don't know what you mean by Debra

Not if he hit format

If the playback device doesn't have to transcode, 1G is more than sufficient. Devices connected via WiFi introduce other complications since the bandwidth varies considerably

If deleting and recreating the image doesn't work, then there's other issues at play here, which will take more investigation.

Have you tried "Remove server"?

That would be v1, which is long deprecated in favour of the tarballs. Problem with that method is a fair amount of users suffered crashes of the system when the backup ran due to just bombing the system with potentially a million symlinks when doing the backups of certain apps (ie: Plex) You can always run an appropriate cp command yourself on a schedule.

Did you AT ANY POINT format the drive in the GUI? Parity system is a redundancy to protect against drive failure and cannot protect against file system errors. You need to run the disk check filesystem against the drive (emulated) Post your diagnostics if you need more help.

Today's update brings forth the basis for new features, namely an "Action Centre" (and yes that's spelled correctly, eh) Anything that you have installed which is deprecated / blacklisted, or has an update available for it will appear here. If there is nothing that meets the criteria, then Action Centre will not appear.

How long before it stops responding? 120 seconds exactly?

People would probably be shocked if they realize that I know nothing about actually building a container. What I do know about is the user experience related to installing / updating any given app. Should be fine.

It looks like you've got multiple browser sessions and/or devices still open to the webUI which doesn't help things out. Also, one quirk of the UI is that basically until everything is started then it webUI won't respond to login attempts. IE: After all containers are started (including whatever delays) and the VMs are started will the UI begin to start.

By doing that, you're going to stop anyone who updates from having access to it without also adjusting the template. Can you instead possibly create a config file that dictates which listening port it uses with a default of 8080?

He wants to know if the container port can be changed from 8080 to instead be 80 so that if it's on it's own IP address he doesn't need to append :8080 to the IP address in order to access it. IE: it listens on 80 instead of 8080 Is there a config file or something that dictates the internal listening port

Why would you think that? Safe mode only stops plugins from installing and has no effect on the GUI itself

It's listening on 8080 The host port it's listening on (by the default template) is 1111. As mentioned previously you would have to modify the container to have it listen to 80 (and by inference reply to a separate IP without appending the port #)

In the future, simply attach the diagnostics directly to the post. Many other users (including me depending upon mood) do not like visiting random sites to download the zip file Your issues relate to this May 7 07:09:19 Tower kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 4559, gen 0 May 7 07:09:19 Tower kernel: BTRFS info (device sdb1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 135292, gen 0 Usual cause for corruption on a btrfs cache pool would be memory failing. I'd start by running a memtest for minimum a pass (ideally a couple of passes), especially since it's older memory And I'd guess based upon the size of the image that you're creating (100G) that you've had issues with the image filling up in the past. Review the Docker FAQ, as there's a couple of posts in there about the image filling up. If you can't sort it out, then switch to a docker folder instead of a docker image as it then has the maximum size of the cache pool, but only takes up the amount of space that is currently in use. (Sorting out why though is the preference)

For reference @bonienl Chrome on the left, firefox on the right

There's a PR for what it actually should be. WebUI entries always refer to container port, not the host port. This allows for the user to remap the port easily.

Did you update the nvidia plugin?

You select what you want to install. Also you can select what you want to remove from that section so you don't have to think about them again.

The files have to start with a letter, hence it's renaming

you need to include -M on the at command to have it not send out a notification