furiouslog

It now works again.

Having the same issue right now - Connect didn't recognize my server this morning. I updated the plugin and tried to sign back in, now I can't register the server and I can't connect to it through Unraid Connect.

Let me clarify: when I leave the tab open, it starts logging mce errors after a period of time has passed. If I don't open the tab in a browser and leave it alone, it does not log any errors. I also took the server down and ran another memtest on it, and it passed. All of the system diagnostics that I can run from IPMI also pass. It definitely appears to be a problem related to the other reported problems in this thread of keeping a tab open in a browser.

It only seems to have issues if I leave the webUI tab open. If I close it and leave it alone, everything is fine.

The nginx error has gone away, but I'm getting mce errors and my plex docker spontaneously shut down overnight. I did run memtest (the 64 version) on the memory, so I'm not sure what's up with that, but i'm not getting those endless errors anymore. Does this mean that I need to re-edit that file every time I boot? inverness-diagnostics-20240810-1326.zip

Think I got it this time: cat /etc/nginx/nginx.conf | grep size client_body_buffer_size 32k; types_hash_max_size 2048; client_max_body_size 20m; server_names_hash_bucket_size 128; nchan_shared_memory_size 512M; Now just waiting to see what happens.

Will do - it will take a little time due to competing priorities but as soon as I do that I'll post the results. Thanks for the help!

I added that line in the config, then restarted, and the errors were generated after that. Here's the output: client_body_buffer_size 32k; types_hash_max_size 2048; client_max_body_size 20m; server_names_hash_bucket_size 128;

So I'm running into this now, after upgrading to 6.12.11. It may have been happening before then, but I don't think so. Stuff I have already tried: - Uninstalled Unraid Connect plugin, no effect - Ran Memtest64 - no errors - Changed nchan_shared_memory_size 512M; as suggested - this makes the log size larger but does not prevent the error spam. inverness-diagnostics-20240809-0804.zip Diagnostics attached. Any help or explanation would be awesome.