ZosoPage1963

thanks, that was the issue.

Hi, I started receiving some Out of Memory errors. I have attached my diags. Let me know what y'all can see, thanks! kashmir-diagnostics-20251022-1526.zip

HI, recently, I have been noticing that all of my dockers that run through SWAG, stop working occasionally. What I am seeing is that the proxy-confs are updated, and I must update the configuration file in that folder to get the appropriate docker to connect correctly to the net through the reverse proxy. That never used to be the case. Is there something that I am missing that will allow the containers to use the reverse proxy even if the conf files are not the current ones? Hope that makes sense.

do I just change the version like this?

Any idea if this is working with other containers? In case it is with only this container, then there is this to help switch to another... which one should I go to (if necessary)?

I turned off GPU transcoding and my users are able to stream again.

Thanks for this, but us noobs that followed Spaceinvader's setup video back when this docker was called Letsencrypt, after doing the above steps, now get errors from the other config files that we modified for the likes of bitwarden, etc. console into the swag container cd into the directory listed in the error message. mv stream.conf stream.conf.old restart swag container. Check logs and you should have the Server Ready line at the bottom

recently, I have been getting these errors. Would like to confirm that they can be ignored. it seems to be occurring each morning after my docker update. Oct 24 04:40:01 Kashmir root: Fix Common Problems Version 2022.10.17 Oct 24 04:40:07 Kashmir root: Fix Common Problems: Error: Machine Check Events detected on your server Oct 24 04:40:07 Kashmir root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. Oct 24 04:40:07 Kashmir root: CPU is unsupported I am on 6.11.0. Waiting for 6.11.2 due to wireguard vpn issues with 6.11.1. TIA kashmir-diagnostics-20221024-1010.zip

nevermind on this, I just went back a version on unraid for now.

Hi, I know this is a real dumb question, but how do I edit this file? Can I do this in terminal? I keep getting a permission issue. Sorry for the lack of knowledge on my side. The more info that can be provided, the better. I am sure I am not the only one that is having an issue with permissions in the flash drive.

well, a quick search on my end would have helped... sorry for the post and I will delete if asked. Is there a fix for this coming up or do I just need to make sure no browsers are left open anywhere?

I am definitely not experienced enough to figure out what is going on with my server. Any help would be appreciated. Started getting this message this morning: Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your diagnostics. Any guidance is appreciated. kashmir-diagnostics-20220328-0832.zip

ended up reinstalling the container, didn't find a good fix to get past this error. (for those that may see this in the future).

Hello all. Have had container running fine for a few years, using SpaceInvaderOne's install video. Noticed that there was an update today and went to update. From the update screen, it was getting stuck at 'deleting old data'. Sometimes it takes a while to do some of the steps, so I closed the browser and walked away. Now, when I try to get in, I keep getting 'update in process'. Any instructions on how to get back in would be appreciated, or should I just wait it out for a while (it has been about an hour now). I did check the config file and showed that the maintenance mode = true, and changed it to false, but no chane with the "update in process".

I am getting the same thing, and it appears that nothing has been scanned for 4 or 5 days. I tried deleting appdata folder rebuilding from scratch, but no luck. Also, I tried deleting the json settings file as mentioned above, and still nothing.