We need a custom close reason for web hosting control panels

Question

As part of our ongoing cleanup of old (and new) web hosting control panel questions, we need a custom close reason for web hosting control panels which explains the issue, why we are unable to accept these questions, and points the user to further information.

Answer 1

I propose that the following close reason be used. Until it is installed as a custom close reason, it can be pasted into the Other custom box:

Questions involving web hosting control panels are off-topic at [sf] because they customize their systems such that normal administration tools and methods no longer apply, and thus require support from the vendor or the web hosting industry. See Where can I ask questions about web hosting control panels?

Raw, for pasting:

**Questions involving web hosting control panels** are off-topic at [sf] because they [customize their systems such that normal administration tools and methods no longer apply](https://meta.serverfault.com/q/8055), and thus require support from the vendor or the web hosting industry. See [Where can I ask questions about web hosting control panels?](https://meta.serverfault.com/q/8094)

Answer 2

I've been using this as a close vote reason:

This question is being voted for closure because the question has made mention that a server control panel is installed on the system. Server control panels can and will modify aspects of a server (including but not limited to system tools, shells, and the kernel itself), that make any and all operations unpredictable. The ServerFault community is largely in agreement that standard and repeatable solutions are unlikely and inconsistent results are so common that we often choose to close questions sush as that.

Which could be re-written for a closure reason (as opposed as just a voting to close reason):

This question was closed because it involves, whether directly or indirectly, a server control panel. Server control panels can and will modify aspects of a system (including but not limited to default system tools, standard packages, shells, and the kernel itself), which makes any and all operations unpredictable. As a result the ServerFault community cannot offer standard and repeatable solutions to any problem, no matter how tangentially related.

Add links as necessary? There seems to be a metric-bazillion different FAQs, links, canonical answers, and the like that have been referenced concerning this topic.