Calpulz

So I tried downgrading to 6.12.2 but no luck The GUI still only works properly when using local IP

Exactly the same problem here. Everything been working fine for over a year running unraid 6.9.2. Updated to 6.12.4 yesterday and now getting this problem. Viewing Unraid GUI using local IP everything works fine, but using my domain name which is routed through Nginx Proxy Manager and I get these problems. Websocket is already enabled. Tried 3 different browsers and different computers with same results.

Just gave it ago to no avail Still no sensors. Thanks though. I dont think its the plugin as such since modprobe from the consol shows no sensors either.

Think im already running that. Using a custom kernal from ich777 6.9.0 Beta30 with Nvidia and DVB drivers (for my TV tuners) Thanks tho. Yeah guess ill wait for ryzen 5000 to become more of a thing in the unraid space

I have no idea whats wrong then.. doing modprobe on k10temp and nct6775 shows no results.

Thanks for reply, yeah ive done alot of digging and x570 apparently didn't work on kernal 4.x but 5.x added the support for these drivers. But im already running 6.9.0 beta 30 with kernal 5.8.13 so i think its something to do with asus boards as i have seen asrock working fine. They get detected in sensors-detect but sensors says no sensors found. Thanks though ill have to keep digging

So im running Ryzen 5900x on Asus Strix X570 board. Motherboard USB and AUDIO passthrough only work on Unraid 6.9.0 Beta30 otherwise unraid completly crashes. I also have TV tuners so im currently using the precompiled kernal 6.9.0 Beta30 with DVB drivers (thanks for this!). Everything works fine other then system temperatures. I believe this is due to missing drivers? Driver shows up as "k10temp nct6775" but i get no options for temperature sensors. A little bit out of my depth but is there a kernal that has the correct drivers precompiled or can anyone shed some light on this? Thanks!

I had a thought, maybe its due to the threadripper having multiple numa nodes. So restricting the cores for the container keeps it inside a single numa node instead of having access to all cores across multiple numa nodes? I know some games dont like working across numa nodes (think gta is one of them). Might be completly wrong as i dont fully understand it.

No i still havent found a solution. I have kind of just put up with it. I will try what you suggested and assign some cores to the container. UPDATE: So far so good!! The best ive been able to get is about 10 or 15 minutes before GUI locks up or the container crashes and restarts. Done as you suggested and assigned 4+4HT to the container and i have had the GUI up for 40 minutes now with no crash, reset or freeze. No threads pinned at 100%. Amazing, thanks for figuring that out, i never thought of trying something so simple. Had this issue for months and been driving me crazy!! I wonder why having access to all cores causes this issue though? Seems like it might be something relating to threadrippers.

Hi, posted a while ago about rtorrent pinning a random thread at 100% usage. GUI completly locks up. Still havent managed to sort this, seems to only do it when im downloading. Have a thread ripper 1920x. If anyone can help or point me in the right direction that would be great.

Sorry if this has already been answered or spoken about. But im having GUI lock up due to cpu thread getting pinned at 100%. Ive tried the -t option in extra parameters but doesn't seem to make a difference. Have a threadripper 1920x and its just locking one thread at 100% and randomly changes which thread its using. Then the GUI sometimes comes back for a moment or everything crashes and restarts back up. Any ideas?