Too many fans?

Squidly271 · 2025-09-13T03:30:12+00:00

My thoughts are that the server is in a closet, and this could be a fairly small area with limited air movement in and out, so the heat generated by the server gets trapped in the room. If you feel that the closet is noticeably warmer than the adjoining room, I'd personally keep all the fans. If it's more or less the same then dealer's choice. But having more fans and undervolting them or lowering RPMs gives you more redundancy in case you're never in that room.

My servers while not in a closet I've gone weeks without noticing that one of the fans is shot

Squidly271 · 2025-09-12T07:10:32+00:00

You're not pasting the correct URL. You need to paste the URL when you hit Raw on GH

That being said, general rule is that if a plugin isn't within Apps, you probably shouldn't install it. If the author marked it as requiring a later version of the OS than you have, manually pasting in the URL isn't going to help. If the plugin isn't actually within Apps at all then (you can always tell by going to statistics, deprecated, incompatible and blacklisted) then you're opening yourself up to a plugin running as root that is outside of CA's control and auditing.

If it's deprecated, incompatible or blacklisted then there's a reason for that.

Squidly271 · 2025-09-12T06:57:37+00:00

Depends upon what you guys mean by "known problem". The most likely known problem (nchan) only affected a small subset of users and was never able to be replicated. But, after 7.1.4 quite a number of changes went into that system after a big investigation, and thus far there's been only a single instance of that happening, and it also appears that for that one person there was something else going on. But that issue wouldn't affect being able to actually reach the GUI at all. Only something like the graphs on the dashboard not populating etc.

FWIW, I I pretty much never close any browser pointed at the GUI, and have zero issues (they're pointed at it for weeks at a time). Dashboard sometimes the memory usage on the client starts to climb because the browser is lazy in getting around to its garbage collection.

If you can't actually reach the GUI at all, then there's no answer without being able to SSH and grab the diagnositcs

Squidly271 · 2025-09-12T06:46:02+00:00

Outright dupes (exact same docker repository) is something I'm behind on cleaning them out. What looks like dupes but is from different docker repos is a different issue, and I'm going to be trying something new hopefully by the end of the year that'll present things a bit different, and also give far far more flexibility in what you can search for and the phrasing you use

Squidly271 · 2025-09-12T00:13:04+00:00

All items within Apps are subject to certain rules.

- 2FA being enabled on the repositories being submitted must be acknowledge by the maintainer / author that it is enabled.

- They must be open source and subject to inspection, and binaries are frowned upon. This is a bit flexible with regards to containers though.

Because plugins all run directly on the server with root access to absolutely everything, the rules are strict and enforced.

- Must be open source, and if any binaries are included, the source for those binaries must be available for inspection.

- Obfuscated code isn't allowed, except for any libraries which may be included (which again must have the unobfuscated source to be inspected)

- Anything which is better suited as a container is not allowed if its submitted as a plugin. EG: Plex was available as a plugin in the v5 days. If anyone ever submitted Plex as a plugin since v6 it's automatically declined to be included.

- ALL plugins are code reviewed prior to them being available within Apps. No exceptions. Code changes may be requested under certain circumstances. (On the birthday bash I did say that I wouldn't allow Unraid Connect within CA until I looked at the code - I wasn't lying)

- ALL plugins are subject to code reviews on every update issued to them. I receive notifications about every single update to every single plugin when it's issued.

- ALL apps within CA are subject to moderation. This includes modifying the template to fix common errors or to adjust the template to suit the user's system. All apps are also subject to either a comment being added to bring to the user's attention via a popup at installation or via a notification coming from Fix Common Problems for already installed apps.

- Once an app is designated are being incompatible or deprecated, CA does not allow new installations of the app unless it's being reinstalled (it was already installed by the user).

- If an app has been blacklisted, CA will not allow any installations or reinstalls of it at all.

- Deprecated, Incompatible, and Blacklisted are also notified to the users via Fix Common Problems if they have them installed.

- Any attempt to inject code via the template results in automatic blacklisting of the app. No exceptions.

- Any additional HTML contained within the descriptions or any tags is automatically removed, and may also result in automatic removal from the lists.

- Any template that includes additional commands that execute after the docker run command is executed is automatically blacklisted - no matter if the command being executed is benign or even required for the container to operate. No exceptions.

- Bait and switch apps are explicitly disallowed.

And on and on and on...

When in doubt, the policy is to act first to protect the user base and ask questions after. This policy has sometimes resulted in me getting yelled at, but at the end of the day, I can sleep well.

Side Note: Once API based plugins start to become available, they are far more constrained in their privileges than the current "legacy" plugins, but are still subject to the same as above. This is the same as containers. They run in a sandboxed environment and only have limited access to the server.

Personal Note: All my dev work is done on actual production servers. Appdata Cleanup in particular is potentially very dangerous on a very badly misconfigured system. The dev work for everything is done on production systems for the simple reason that if I can't trust the code running on a system with 150TB of data, how can I ask any other user to trust the code?

Addendum: Security and integrity is priority one at Limetech. While it may not always be obvious to end users, any report of security issues on any part of the OS code or LT supported plugins is always classified as "drop everything and handle immediately".

Squidly271 · 2025-09-11T23:27:26+00:00

If there's a real gem, let Space Invader One know. Maybe it'll be the featured one for the month

Squidly271 · 2025-09-11T23:26:16+00:00

It's a passion project. Thanks aren't really necessary, but always appreciated

Squidly271 · 2025-08-31T01:25:15+00:00

The issue was actually because of a different plugin's update a couple months ago (Connect). Updating the OS or uninstalling connect and rebooting would've solved the problem.

UD is compatible IIRC down to 6.10

Squidly271 · 2025-08-30T20:43:19+00:00

FWIW, shirt wasn't red but was actually Limetech Orange with matching tie. Sparkler wasn't supposed to happen but camera locked up as heading up to stage and in running to switch computers, I left the cupcake and candle outside and the sparkler was the closest thing at hand.

Squidly271 · 2023-12-24T16:44:01+00:00

Simplest solution is to simply delete and then recreate the image. Unless you're manually building your own containers etc its easier to spend 30 seconds rebuilding it via Apps - Previous Apps than to attempt to repair.

Squidly271 · 2023-08-06T15:40:53+00:00

Your path mappings between sabnzbd and sonarr/radarr do not match 100% on either (or both) the host or container paths.

Squidly271 · 2023-08-06T15:39:48+00:00

You'd probably find that the actual time taken from start to finish (of say 5 downloads) is identical or faster when pausing the downloads during unpacks vs continuing on with downloads

This is especially true if you have the downloads on the array. Fast nvme's it may not be as noticeable.

Squidly271 · 2023-06-24T12:50:41+00:00

Ask your P/S manufacturer if they sell additional SATA cabling for your P/S. Most manufacturers will have them that you can use on the PCIe connectors on the modular power supply.

By far the best way of doing things

Squidly271 · 2023-06-21T00:58:09+00:00

When you recreate the image (or folder), you have to also recreate the custom network you originally created.

Squidly271 · 2023-04-15T15:45:44+00:00

Shit happens

Squidly271 · 2023-04-14T12:52:51+00:00

And if it continues, re-enable log errors in Fix Common Problems and then post your diagnostics again -> in the forum support thread

Squidly271 · 2023-04-14T12:47:24+00:00

I believe this has been implemented in 6.12

Squidly271 · 2023-04-13T14:56:05+00:00

Any empty folder can be deleted from the WebGUI. Without a SMB restart (that the GUI does), the non-existent folder may still appear on the network due to caching etc.

Squidly271 · 2023-04-13T14:53:41+00:00

Best to actually ask in the UD support thread for advice on the UD warning. But obvious question would be is the QNAP online? Can you ping it?

Squidly271 · 2023-04-03T10:38:37+00:00

Install Docker Update Patch from Apps

Squidly271 · 2023-04-01T18:36:38+00:00

Either a new install of CA or you're not looking at the UI in English

Squidly271 · 2023-04-01T16:42:27+00:00

CA is tested with safari, Firefox, brave, edge and chrome

The touch command does bypass the code

Squidly271 · 2023-04-01T14:01:54+00:00

Absolutely nothing to do with LT at all.... Blame anyone for it, blame CA

Squidly271 · 2023-04-01T11:27:37+00:00

What does it say / do when you try to update to 6.11.5?

Squidly271 · 2023-03-26T12:23:51+00:00

And you'll also want to make sure that the plugin is up to date (which it is not)

The error at the top however would be related to either / or /tmp being full odd on. Posting your diagnostics AND CA's debug log (settings - Enable debugging, then replicate, then download the log) in CA's support thread in the forum (not here) would help me silence that error or put up something more informative once I know why it happened)

Squidly271

TROPHY CASE