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

Hey Ed, i'm really hitting the wall with this tutorial. I'm going through the reverse proxy but the application never askes me to sign in and it crashes my browser and continually disconnects me when I create a room. What info can I provide that could help you figure me out... LOG: focus.jitsi.meet : [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-set-timezone: executing... WARNING: CSTUS is not a valid time zone. [cont-init.d] 01-set-timezone: exited 0. [cont-init.d] 10-config: executing... FATAL ERROR: Jicofo component secret and auth password must be set [cont-init.d] 10-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. LOG video.meet.jitsi: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-set-timezone: executing... WARNING: CSTUS is not a valid time zone. [cont-init.d] 01-set-timezone: exited 0. [cont-init.d] 10-config: executing... FATAL ERROR: Jicofo component secret and auth password must be set [cont-init.d] 10-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. LOG: xmpp.meet.jitsi: [cont-init.d] 01-set-timezone: exited 0. [cont-init.d] 10-config: executing... FATAL ERROR: Jicofo component secret and auth password must be set [cont-init.d] 10-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. Thanks in advance for any help..

Kinda interesting since this morning my large server with dual 2GHz processors has been at an idle while connected to the Rosettta@home client. I restarted the docker to make sure nothing broke and after it connected again it is still not being utilized. My faster machines are still hard at work leading me to believe that they now have so much surplus of available machines they now may be utilizing only the faster equipment in the pool. This is a good thing and more than enough in this effort is a blessing. If I don't see activity by tomorrow I may assign the slower server to another service so it too will be getting used in a productive way. Either way I'm tickled that our group has shown so much compassion and human spirit in this crisis.

Thank you guys for helping us to help them in this dire time. Feels good to do something!