cpshoemake

Is there any way to get the syslog collector to work?

Great work GuildDarts! I'm not sure "Docker Folder" does it justice. The organization is great, but the real feature is the ability to stop and start groups of dockers. I'm doing so much less clicking now. Feel free to put up a donate button. I'd be happy to throw a few bucks your way for this.

My sqlite database was getting pretty big so I just muddled through migrating to a PostgreSQL11 database. Here are the steps, for posterity, if anyone is interested. Backup your /appdata/quassel-core directory in case something goes wrong Install the Postgres11 container from postgres. Change the POSTGRES_PASSWORD variable to whatever password you like. The rest are fine at default, unless you have a port conflict or want to change your storage path. Hit "Apply" to start the container. Open a console on the new container. Enter the following commands: # psql -U postgres psql (11.7 (Debian 11.7-2.pgdg90+1)) Type "help" for help. postgres=# CREATE USER quassel ENCRYPTED PASSWORD 'yourpassword'; CREATE ROLE postgres=# CREATE DATABASE quassel WITH OWNER quassel ENCODING 'UTF8'; CREATE DATABASE Open a console to your Quassel container. Enter the following commands: # quasselcore --configdir=/config --select-backend=PostgreSQL [Info ] SQLite storage backend is ready. Schema version: 31 [Info ] Database authenticator is ready. Default values are in brackets Username [quassel]: <-- Leave this at default (just hit Enter) Password []: <-- Enter the password you used for the quassel database Hostname [localhost]: <-- Enter your Unraid IP address Port [5432]: <-- Leave default unless you changed the port Database [quassel]: <-- Default At this point I got a bunch of errors, but everything worked out anyway. You will now see the window start to fill with asterisks as your old database is migrated. This could take awhile depending on the size. Once the asterisks stop and you get a prompt back, restart the Quassel container. Connect to your core and make sure all your settings and data are intact. If everything is good, you can now delete the /appdata/quassel-core/quassel-storage.sqlite file Profit!

https://plex.mydomain.com works fine for me.

It's not that smart. Files are evaluated one-at-a-time. Your subtitle file met all the requirements and was moved to disk 1. The mkv was evaluated next and your split level and mostly-full disk prevented the mkv from moving. I spent way too much time futzing with this in the past. Eventually I lost patience and set everything to "most-free" and "split any directory as required."

I had this problem with a Seagate IronWolf drive (ST8000VN0022). The write cache was disabled and none of the sdparm or hdparm commands would enable it. I was finally able to fix it with SeaChest utilities (https://www.seagate.com/support/software/seachest/). The download includes a boot drive creation tool. I booted a second system into this Linux environment and the following command fixed the issue for me: SeaChest_Configure -d /dev/sg0 --sctWriteCache enable

Thanks. I renamed the file to default.old and left it in the folder. Moving it out fixed it. Compare the new config to your old one. Are you missing the following lines? Are they commented out? Add or uncomment them. add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Frame-Options "SAMEORIGIN";

That is the correct file. Nextcloud's /config directory is mapped to /appdata/nextcloud by default in the docker template. Make sure you get a backup, as I'm getting 504 errors after deleting it. I haven't been able to figure out what the problem is.

I tried to implement the fix from https://blog.linuxserver.io/2019/10/26/psa-nextcloud/ but ran into a 502 error with the new config. Is there something from the old config that I need to copy over? Here are my old and new configs. default.old default

If I select "No" to "Let scheduled mover run during a parity check / rebuild" in the Mover Tuning options, the mover will not run if there is a paused parity check in progress. Is this expected behavior?

Thanks Squid! You're my hero. I've set CPU priority to "Very Low' and disk i/o priority to "Idle." This seems to have solved all my issues with the mover stalling other processes.

I have this problem as well. Plex will play for a few seconds and buffer for a few seconds, repeating until the mover is done. Is there a way to lower the priority of the mover?

I think it's an issue with Chrome. I remember that happening when I used Chrome in the past. It doesn't happen with the Brave browser I use now.

Open appdata/letsencrypt/nginx/site-confs/default. Uncomment (delete leading #) lines 5-10. That tells nginx to redirect http traffic to https. Just in case you have a different version of the file, these are the relevant lines: server { listen 80; listen [::]:80; server_name _; return 301 https://$host$request_uri; }

Mine looks just like that on 2019.01.22.