Introduction #

Some features in cPanel are intentionally disabled on all ProRedLine packages. This is a deliberate platform decision and not a technical issue. Disabled features cannot be enabled by customers. In this doc we will explain more.

---

Why Features Are Disabled #

Some cPanel features may be disabled intentionally. This is done to help improve platform security, reduce the available attack surface, avoid deprecated or unstable components, prevent misconfiguration, and keep the hosting environment as consistent and reliable as possible.

In practice, this means certain tools are not enabled if they do not fit the way the platform is configured or if they could introduce unnecessary risk, confusion, or instability. Limiting access to unsupported or unnecessary features also helps maintain a cleaner and more predictable hosting environment.

For that reason, only features that are relevant, supported, and appropriate for the platform are enabled.

---

Disabled Features on All Packages #

The following cPanel features are disabled across all ProRedLine subscriptions:

• Agora Shopping Cart
• API Shell (for developers)
• BoxTrapper
• Dynamic DNS
• Email Delivery Route (deprecated)
• FTP Settings
• Mailing Lists
• Perl Modules
• PHP Pear Packages
• phpPgAdmin
• PostgreSQL
• Raw Access Logs
• Ruby on Rails
• RubyGems
• Site Quality Monitoring Plugin
• Sitejet Builder Plugin
• Social Media Management Plugin
• SSH Access and Terminal
• Theme Switching
• Webalizer

Reasons for Specific Features Being Disabled #

Some features are disabled because they rely on deprecated or legacy software that is no longer actively maintained or recommended. Keeping such components available can introduce unnecessary complexity and may no longer align with a stable and supported hosting environment. Examples of this include tools such as Email Delivery Route, Webalizer, and Agora Shopping Cart.

Other features may be disabled for security and abuse prevention reasons. Certain tools can increase the risk of misuse, unintended access, or unnecessary exposure of sensitive functionality. Where possible, safer or more suitable alternatives are used instead. Examples include SSH Access and Terminal, API Shell, and certain FTP-related settings.

Some technologies are also disabled because they are outside the supported environment. Not every language, framework, or platform is included as part of the hosting setup, and unsupported components are not enabled by default. Examples include Ruby on Rails, RubyGems, Perl Modules, and PostgreSQL. In this environment, web hosting is focused primarily on PHP-based applications.

Features may also be disabled to maintain platform consistency. Tools or plugins that significantly change site behaviour, workflows, or the expected hosting environment may be limited in order to keep the platform predictable and easier to support. Examples include Theme Switching, the Sitejet Builder Plugin, and the Social Media Management Plugin.