PilotReelMedia

Excellent! Thanks so much. Worked like a charm!

I'll give it shot in the morning. Thanks for your solution.. I'll post if it resolves my issue..

Thanks for saying so. Always nice to know you are not alone. I think the update came from a different repository and will require adjustments for it to work the way the old one did. I spent a day trying to fix it and I'm done.

Last swag docker update caused a issue with my ability to published my instance of nextcloud out to my duckdns subdomain. On swag boot I get the initial repot in the log: **** The following active confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare the following files to the samples in the same folder and update them. **** **** Use the link at the top of the file to view the changelog. **** ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐ │ old date │ new date │ path │ ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤ │ 2020-10-04 │ 2022-08-16 │ /config/nginx/nginx.conf │ │ 2020-06-02 │ 2022-08-20 │ /config/nginx/ldap-server.conf │ │ 2020-05-31 │ 2022-09-22 │ /config/nginx/authelia-server.conf │ │ 2020-05-31 │ 2022-08-20 │ /config/nginx/authelia-location.conf │ │ 2020-10-29 │ 2022-08-20 │ /config/nginx/ssl.conf │ │ 2020-10-04 │ 2022-09-01 │ /config/nginx/proxy.conf │ │ 2020-12-09 │ 2022-10-28 │ /config/nginx/proxy-confs/nextcloud.subdomain.conf │ │ 2021-01-03 │ 2022-10-03 │ /config/nginx/site-confs/default.conf │ └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘ [custom-init] No custom files found, skipping... [ls.io-init] done. Server ready Then I get a spamming message in the log : nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 local port still works but the subdomain just times out. Can anyone help me? Thanks. Version 6.11.5

Just realized Unraid automagically disables lid switch functions. Brilliant!

Just realized that this brilliant software already disables the lid close shut down feature. lol

Was hoping a I would be able to perform a edit to a conf file like on Linux to adjust lid functions and run Unraid lid closed on my old Asus Gaming Laptop. Any suggestions?

I came across this topic and it relates to a project I am working on. I'm installing unraid on a old Asus i7 laptop and was hoping to be able to nano edit the systemd/logind .conf and adjust the lid actions so I could run with the lid close. That seems to be different on unraid. Any suggestions?

I have a similar issue. When I check system devices this error message is pointing to this: "00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06)" Log spam is: (kernel: i801_smbus 000:00:1f.3: SMBus is busy, can't use it!". Don't have a clue what to do to fix it though speedwagon-diagnostics-20211115-1814.zip

I think I'm having this issue. I have included my diagnostic zip. Did not see a resolution here.speedwagon-diagnostics-20211115-1814.zip

Yeah I'm a derp... Thank's jonathanm...

Okay I think I found the culprit... Krusader is showing as 125G. I am doing a back-up of a 600G windows 10 image. I had know idea Krusader would occupy so much space as a docker image.

Thank you for your help itimpi...

Yes. It is no longer present. Krusader nor Win Explorer see the vdisk. I'll see if there something else taking up space but there was literally no change when I remove a 100G VM. Does it take time for the space to show as free?

Deleted a Linux VM and it's image from the drop down menu on dashboard. Was going to add a new cache pool dedicated to host this vm and free space on original cache. I did not however get the space back and I assume this is because the creation of the Linux VM created a Linux partition within the cache drive and although the image was remove it did not remove the formatted space. Is this a good assumption and if so can it be re formatted or reclaimed without formatting the entire drive?