¡Oferta!

CWP7 Turbo Manager

El precio original era: 120,00 €.El precio actual es: 67,00 €.

CWP7 Turbo Manager is an intelligent performance auditing, optimization and monitoring module built specifically for CWP7 / Control Web Panel administrators.

Turn complex server tuning into a safe, guided GUI workflow. CWP7 Turbo Manager automatically analyzes PHP-FPM, OPcache, Nginx FastCGI cache, server resources and every hosted website, detects real performance bottlenecks, and recommends server-specific optimizations based on actual measurements—not generic presets.

Preview every change before applying it, with automatic configuration backups, syntax validation, safe service reloads, website regression testing and one-click rollback protection.

Key features include intelligent OPcache tuning, account-level PHP cache analysis, Nginx tracking-URL cache optimization, WordPress/WooCommerce cache-safety testing, scheduled post-tune verification, professional before/after reports and commercial CD-key licensing.

Measure. Optimize. Verify. Protect.

A must-have CWP7 performance toolkit for hosting providers, developers, agencies and professional server administrators.

Descripción

CWP7 Turbo Manager – Intelligent Performance Auditing, Optimization & Monitoring for CWP7 Servers

CWP7 Turbo Manager is a professional performance auditing, optimization, monitoring, regression-testing, and servidor-tuning module designed specifically for administrators running CWP7 / Control Web Panel servers.

If you manage websites, WordPress installations, WooCommerce stores, PHP applications, Joomla websites, alojamiento accounts, PHP-FPM pools, Nginx FastCGI cache, or multiple customer websites from CWP7, then you already know how difficult performance troubleshooting can become.

A servidor may look healthy at first glance while PHP OPcache is completely exhausted. A WordPress site may load quickly from cache but take several seconds when a visitor uses a tracking URL. A WooCommerce website may accidentally cache a functional query. PHP-FPM may be active but configured inefficiently. Nginx may appear correctly configured while certain cache-key rules create duplicated cache entries or even cache collisions. One website may be fast while another account quietly consumes almost all available OPcache memory.

Finding these problems manually normally requires SSH access, Linux knowledge, PHP-FPM inspection, OPcache debugging, Nginx configuration analysis, repeated CURL tests, WordPress knowledge, cache investigation, command-line tools, and a great deal of time.

CWP7 Turbo Manager brings that entire workflow directly inside the CWP7 administrator panel.

Instead of guessing, CWP7 Turbo Manager measures the servidor, analyzes the results, identifies real bottlenecks, explains what is happening, proposes safe performance presets, shows the exact changes before they are applied, creates backups, validates the configuration, reloads only the required services, runs website regression tests, and provides rollback protection.

The goal is simple:

Measure first. Understand the bottleneck. Optimize only when justified. Verify the result. Protect the servidor.

¿Por qué? CWP7 Turbo Manager Is Different

Many so-called servidor optimization tools use generic recommendations such as:

“You have 8 GB RAM, therefore set OPcache to 512 MB.”

That approach ignores the real workload of the servidor.

CWP7 Turbo Manager takes a completely different approach. It measures actual resource usage before recommending a change.

For example, the module can detect that PHP 8.3 is configured with 128 MB OPcache memory, that all 128 MB are being used, that no memory remains free, that the interned strings buffer is full, and that thousands of PHP scripts are competing for limited cache space.

At the same time, PHP 7.4 on the same servidor may use only 22 MB of its available 128 MB and therefore require absolutely no optimization.

CWP7 Turbo Manager understands the difference.

It does not blindly optimize every PHP version simply because a generic rule says that bigger values are better.

This makes the module particularly valuable for real alojamiento environments where multiple PHP versions, customer accounts, WordPress sites, WooCommerce stores, Laravel applications, Joomla websites, and custom PHP software may coexist on the same machine.

Complete CWP7 Performance Command Center

After installation, CWP7 Turbo Manager appears directly inside the CWP7 administrator interface.

The administrator receives a centralized performance dashboard containing servidor health information, website measurements, PHP-FPM status, OPcache statistics, Nginx FastCGI cache information, recommendations, regression testing, backup history, rollback controls, licensing information, post-optimization follow-up monitoring, and downloadable performance reports.

Normal operation is GUI-first.

You do not need to repeatedly connect through SSH just to inspect OPcache, run website tests, analyze Nginx caching, or verify a performance change.

CWP7 Turbo Manager provides a guided workflow designed to help both experienced servidor administrators and alojamiento professionals who want a safer and faster way to maintain CWP7 systems.

Guided Performance Workflow

One of the most powerful features of CWP7 Turbo Manager is the Guided Performance Workflow.

The administrator can run a complete safe workflow that performs read-only measurements across the servidor before any configuration change is proposed.

The workflow includes:

  • Servidor Audit – checks CPU load, RAM, swap, disk usage, PHP-FPM services, OPcache configuration, Nginx configuration and detected HTTPS websites.
  • Website Regression Testing – verifies HTTP responses, cache HIT/MISS/BYPASS behavior, tracking URLs, functional query strings and potential cache collisions.
  • Live OPcache Measurement – measures real shared-memory usage, interned strings, key-table pressure, cached scripts and hit rate.
  • Intelligent Recommendations – recommendations are generated only when a measurable bottleneck exists.
  • Safe Preset Preview – shows current values, proposed values, expected impact and exact configuration changes.
  • Apply + Validate + Verify – backs up the original configuration, validates syntax, reloads the appropriate service and verifies the result.
  • Post-Tune Monitoring – performs scheduled follow-up checks to ensure the optimization remains healthy after the system has warmed up.

The safe workflow itself does not silently modify the servidor.

Configuration changes always require administrator approval.

Intelligent PHP OPcache Analysis

PHP OPcache is one of the most important performance components on a modern PHP alojamiento servidor, but it is also frequently misunderstood.

A servidor can have plenty of free system RAM while OPcache itself is completely full.

CWP7 Turbo Manager measures OPcache directly through the appropriate PHP-FPM environment and displays detailed information for every detected PHP version.

The module can analyze:

OPcache memory usage, free memory, cache-full status, interned strings usage, free interned-string memory, cached script count, cached key count, maximum key capacity, OPcache hit rate, and memory consumption by alojamiento cuenta.

This is particularly important because OPcache pressure does not always mean that the main memory allocation is too small.

The module can distinguish between different types of pressure, including:

memory pressure, interned strings pressure, key-table pressure, fragmentation/allocation pressure, and healthy OPcache conditions.

This prevents unnecessary tuning.

For example, if OPcache still reports a full state while significant memory remains available, the real bottleneck may be the accelerated-file/key table rather than memory itself.

CWP7 Turbo Manager can identify that condition and recommend increasing opcache.max_accelerated_files instead of blindly doubling the OPcache memory allocation.

OPcache Usage by Alojamiento Cuenta

On shared or multi-account servers, it is extremely useful to know which accounts are consuming the PHP cache.

CWP7 Turbo Manager can display OPcache usage by account or filesystem path.

An administrator may discover that one WordPress installation is using more than 100 MB of OPcache while several other sites use only a few megabytes.

This information can help identify large frameworks, plugin-heavy WordPress installations, WooCommerce stores, development projects, abandoned applications, or websites that may need further optimization.

Instead of viewing OPcache as a mysterious servidor-wide number, administrators can understand where the resources are actually being consumed.

Smart OPcache Tuning

When CWP7 Turbo Manager detects genuine OPcache pressure, it can generate a Smart OPcache Tune recommendation.

The preset is based on the live servidor measurements rather than copied from another servidor or selected from a generic template.

Before anything is changed, the administrator sees:

Current configuration → live measurements → detected bottleneck → recommended configuration → reason for the recommendation → estimated resource impact.

The Apply button becomes available only after the recommendation has been previewed.

The reviewed preview is bound to the current servidor identity, PHP version and configuration fingerprint.

If the underlying configuration changes before the administrator presses Apply, CWP7 Turbo Manager refuses to apply the stale preview and requires a fresh measurement.

This is an important protection for production servers.

Automatic Backup and Rollback Protection

Servidor optimization should never mean editing configuration files without a recovery path.

Before applying a supported performance preset, CWP7 Turbo Manager creates a backup of the original configuration.

After writing the proposed configuration, it validates the target service before completing the operation.

For PHP-FPM tuning, the appropriate PHP-FPM configuration is validated before the service is reloaded.

For Nginx changes, CWP7 Turbo Manager runs an Nginx configuration syntax test before reload.

If validation fails, the change is not allowed to remain active.

Backup records are shown inside the GUI under Backup & Rollback History.

Administrators can see which component was modified, when the change occurred, which original file was backed up, and use the Rollback control if necessary.

Advanced Nginx FastCGI Cache Analysis

FastCGI caching can make WordPress websites extremely fast, but an incorrect cache configuration can create serious problems.

CWP7 Turbo Manager analyzes the active Nginx configuration and looks specifically at FastCGI cache-key behavior, query-string handling, internal WordPress/Joomla rewrites, and tracking URL normalization.

One particularly dangerous configuration pattern involves using a cache key based on the internally rewritten $uri.

WordPress pretty URLs can internally resolve through /index.php. If the wrong cache key is used, different public pages can potentially collapse onto the same cached object.

CWP7 Turbo Manager is designed to recognize this type of risk.

The module can use the original browser-request path while still allowing safe tracking-only URLs to reuse the clean-page cache.

Tracking URL Cache Normalization

Modern advertising, analytics, marketing por correo electrónico and affiliate systems frequently add tracking parameters to URLs.

Examples include:

utm_source, utm_medium, utm_campaign, _gl, _ga, gclid, fbclid, msclkid, gbraid, wbraid and similar identifiers.

On many Nginx configurations, every URL containing a query string bypasses FastCGI cache.

This means that a perfectly cacheable WordPress page can suddenly require a full PHP/MySQL request simply because the visitor arrived from Google Ads, Facebook, an email campaign or Google Analytics cross-domain tracking.

CWP7 Turbo Manager can detect this behavior and identify it as a performance opportunity.

The Safe Nginx preset can normalize tracking-only URLs so they reuse the same clean-page cache while preserving bypass behavior for functional parameters.

That means:

/page/?utm_source=facebook can safely reuse the clean /page/ cache, while requests such as ?s=search, ?orderby=price, ?add-to-cart=123, cart sessions, WooCommerce checkout requests and logged-in WordPress sessions remain protected by the existing bypass logic.

Website Performance & Cache Regression Testing

Changing servidor performance settings without testing websites afterward is risky.

CWP7 Turbo Manager therefore includes a dedicated Website Performance & Cache Regression Test sistema.

Each detected HTTPS virtual host can be tested directly against the origin servidor.

The system can inspect:

HTTP response, homepage TTFB, FastCGI cache status, tracking parameter behavior, functional query bypass behavior, internal-page cache separation, and potential cache collisions.

Results are classified intelligently as:

PASS, REVIEW, ACCEPTED, FAIL or SKIPPED/INCONCLUSIVE.

A red FAIL is reserved for verified critical conditions.

Redirects, 404 candidates, empty pages and inconclusive internal-page comparisons are not automatically treated as cache-collision failures.

This dramatically reduces false positives.

CMS-Aware Testing

CWP7 Turbo Manager attempts to identify common application types including WordPress, WooCommerce, Joomla and other PHP applications.

This matters because not every website should be judged using the same criteria.

A static or cached WordPress homepage may respond in a few milliseconds, while a dynamic Laravel application or CRM may intentionally bypass FastCGI caching.

A WooCommerce site requires additional caution because cart, checkout, session cookies, product filtering, sorting and add-to-cart functionality must never be blindly cached.

CWP7 Turbo Manager focuses on evidence rather than forcing every application into one generic configuration.

Scheduled Post-Tune Follow-Up

A configuration change can appear successful immediately after it is applied but behave differently after the servidor has handled real traffic.

CWP7 Turbo Manager therefore includes scheduled post-optimization follow-up monitoring.

Successful supported tuning operations can schedule additional measurements after approximately:

10 minutes, 1 hour and 24 hours.

These follow-ups can verify that OPcache remains healthy, key-table utilization remains reasonable, interned strings have sufficient headroom, websites continue responding, and no new regression appears after normal traffic has warmed the servidor.

This is particularly useful for OPcache because the hit rate immediately after a PHP-FPM reload can be misleading. The cache has just been recreated and needs time to warm.

CWP7 Turbo Manager distinguishes post-reload warm-up measurements from mature cache behavior.

Professional Before & After Verification

After a successful optimization, the GUI can display a before-and-after verification report.

For example:

Before: OPcache full, zero free memory, key table 100% utilized.

After: hundreds of megabytes free, key-table utilization reduced dramatically, interned strings with safe headroom, websites regression-tested successfully.

This gives the administrator evidence that a change actually resolved the measured problem.

The goal is not simply to modify configuration values.

The goal is to prove that the modification produced a healthier servidor state.

Exportable Performance Reports

CWP7 Turbo Manager Commercial Edition can generate professional performance reports for administrators and customers.

Reports can include servidor identity, audit information, website response times, regression status, OPcache measurements, Nginx configuration status, before-and-after tuning results, follow-up verification and rollback information.

Reports can be generated in self-contained HTML format and structured JSON format.

The HTML version can be opened in a browser and printed or saved as PDF.

This makes the reporting system useful for:

alojamiento companies, managed servidor providers, web developers, WordPress maintenance businesses, agencies, internal IT departments, customer support teams and technical consultants.

An administrator can optimize a customer’s servidor and provide clear evidence of what was detected, what was changed and whether performance improved.

Commercial CD-Key Licensing

The commercial edition of CWP7 Turbo Manager includes CD-key licensing designed to work with the Freespirits licensing infrastructure.

The license can be configured as a lifetime, single-servidor activation suitable for a one-time-payment commercial product.

Activation takes place directly from the CWP7 Turbo Manager GUI.

The administrator enters the license key and the module communicates securely with the Freespirits License Manager API.

The license system can validate the product identifier, activation limit, servidor binding and signed license token.

CWP7 Turbo Manager verifies signed license information locally and supports an offline grace period so a temporary licensing-servidor outage does not interfere with the customer’s websites or servidor services.

The licensing layer controls premium module functionality only.

It never shuts down customer websites simply because the licensing service cannot temporarily be reached.

Designed for Production Servers

CWP7 Turbo Manager has been designed around one principle:

performance optimization must never become a bigger risk than the performance problem itself.

For this reason, supported configuration changes follow a controlled process:

Measure → Preview → Backup → Validate → Apply → Reload → Verify → Regression Test → Follow Up → Rollback if necessary.

The module does not intentionally expose unrestricted root-shell execution through its interface.

Its administrator actions are designed around predefined operations and controlled performance workflows.

Who Should Use CWP7 Turbo Manager?

CWP7 Turbo Manager is ideal for anyone responsible for maintaining a CWP7 servidor.

This includes alojamiento providers, freelance system administrators, web developers, WordPress professionals, WooCommerce developers, digital agencies, managed alojamiento businesses, affiliate marketers running multiple websites, SaaS owners, PHP developers, IT professionals and administrators managing customer websites.

If your CWP7 servidor hosts more than one website, the module can save significant troubleshooting time.

If your servidor hosts dozens of websites, it can become an essential daily administration tool.

Why Every CWP7 Administrator Should Have It

CWP7 itself provides powerful servidor-management functionality, but performance troubleshooting frequently requires information from many different layers.

You may need to inspect PHP-FPM, OPcache, Nginx, WordPress, WooCommerce, query strings, servidor RAM, service state, website response times and application-specific behavior before you understand why a website is slow.

CWP7 Turbo Manager brings those performance signals together.

Instead of asking:

“Why is this website slow?”

you can see:

“PHP 8.3 OPcache is full, the key table is exhausted, one account consumes most of the cache, functional queries correctly bypass FastCGI, tracking URLs unnecessarily miss cache, and the database is not the immediate bottleneck.”

That level of information changes servidor administration completely.

It replaces guesswork with evidence.

It can reduce unnecessary plugin disabling, unnecessary database tuning, unnecessary servidor upgrades and risky configuration experiments.

It also provides something equally important: confidence.

When a change is made, CWP7 Turbo Manager can verify that websites still work afterward.

Installation

Installation is intentionally simple.

Upload the downloaded CWP7 Turbo Manager ZIP package directly into the /root directory of your CWP7 servidor.

For version 1.0.0, the uploaded file would normally be:

/root/cwp-turbo-manager-v1.0.0.zip

Connect to your servidor as root and run the following commands:

cd /root && \
rm -rf /root/cwp-turbo-manager-v1.0.0 && \
unzip -o /root/cwp-turbo-manager-v1.0.0.zip -d /root/ && \
cd /root/cwp-turbo-manager-v1.0.0 && \
chmod +x install.sh && \
bash install.sh

The installer places the required CWP7 module files, Turbo Manager engine, configuration files and supporting services into their appropriate locations.

After installation, refresh the CWP7 administrator panel.

You should see:

CWP7 Turbo Manager

inside the administrator interface.

From that point onward, normal performance auditing and optimization are performed through the GUI.

License Activation

Open:

CWP7 Turbo Manager → License

Enter your commercial CD-key and select Activate.

After successful activation, the commercial features become available for the licensed servidor.

The license is intended to be bound to the authorized servidor according to the licensing terms of the purchased product.

Recommended First Run

After activation, the best starting point is the Guided Performance Workflow.

Open:

CWP7 Turbo Manager → Audit Workflow

and select:

Run Safe Workflow

The module will perform the safe read-only analysis first.

Review the servidor audit, website regression results and live PHP OPcache measurements.

If the module identifies an optimization opportunity, preview the recommendation before applying anything.

Only apply a preset after reviewing the proposed change.

CWP7 Turbo Manager will then handle the supported backup, validation, service reload and post-change verification process.

Upgrading CWP7 Turbo Manager

Future versions can be installed over the existing installation using the same general process.

For example, after uploading a newer ZIP package into /root, extract the package and run its installer.

The commercial installer is designed to preserve relevant configuration, licensing state, performance history, rollback records and existing servidor settings where appropriate.

Always use the installation instructions included with the specific version you download.

No More Blind Servidor Optimization

CWP7 Turbo Manager is not designed to make random configuration changes just to make values larger.

It is designed to answer the questions that matter:

Is PHP actually under pressure?

Which PHP version is affected?

Is OPcache memory full?

Are interned strings exhausted?

Is the key table full?

Which account consumes the cache?

Are websites actually using FastCGI cache?

Are tracking parameters destroying cache efficiency?

Do functional WooCommerce queries remain bypassed?

Did the optimization make the servidor healthier?

Did all websites remain operational afterward?

Can the previous configuration be restored?

CWP7 Turbo Manager is built to provide those answers.

Turn CWP7 Performance Management Into a Controlled Workflow

Managing a production servidor should not require remembering dozens of commands every time a performance problem appears.

It should not require manually copying values between terminals, PHP configuration files, website tests and notes.

It should not require applying a change and hoping nothing breaks.

CWP7 Turbo Manager transforms servidor optimization into a structured process that can be repeated consistently across different CWP7 servers.

Each servidor is measured independently.

Recommendations are generated from that servidor’s own workload.

Configuration changes are previewed.

Original files are backed up.

Services are validated.

Websites are regression-tested.

Follow-up checks verify that the improvements remain healthy.

And the entire process is visible directly from the CWP7 administrator interface.

CWP7 Turbo Manager – Measure. Optimize. Verify. Protect.

CWP7 Turbo Manager gives CWP7 administrators something that is normally available only through lengthy manual servidor investigation: a clear understanding of where performance is being lost and a controlled way to improve it.

Whether you manage one important production servidor or operate multiple customer alojamiento environments, CWP7 Turbo Manager helps you find hidden PHP bottlenecks, improve cache efficiency, protect WordPress and WooCommerce behavior, monitor performance after changes and keep a complete history of important optimization actions.

Instead of reacting to complaints that a website “feels slow,” you can measure what is happening.

Instead of copying generic optimization settings from tutorials, you can tune the actual workload.

Instead of changing Nginx and hoping every site still works, you can run automated regression tests.

Instead of forgetting what configuration existed before an optimization, you have rollback history.

Instead of checking once and assuming the servidor will remain healthy, you have scheduled post-tune verification.

And instead of performing the same complicated command-line investigation again and again, you have a dedicated CWP7 performance management interface.

If you administer CWP7 servers professionally, CWP7 Turbo Manager is designed to become one of the first modules you open when performance matters.

Audit smarter. Tune safely. Verify every change. Keep your CWP7 servers running at their best with CWP7 Turbo Manager.

Información adicional

Platform

CWP7 / Control Web Panel

Product Type

Server Performance Optimization Module

License Type

Lifetime / One-Time Payment

Activation Limit

1 Server

License Binding

Server Public IP

Soporte PHP

PHP-FPM Multi-Version Support

Optimization Features

OPcache Tuning, Nginx FastCGI Cache, Website Regression Testing

Safety Features

Backup, Validation, Rollback Protection, Post-Tune Verification

Monitoring

Scheduled Audits, Post-Tune Follow-Up, Website Performance Checks

Reporting

HTML Reports, JSON Reports, Before/After Performance Verification

Changelog

CWP7 Turbo Manager — Changelog

Current Release: v1.3.4

CWP7 Turbo Manager continues to evolve from a performance auditing tool into a production-safe CWP7 optimization, diagnostics, monitoring and recovery platform.

The focus of recent releases has been simple:

Improve servidor performance without introducing unnecessary risk.

Every automated or assisted optimization is designed around validation, backups, conservative decision-making and rollback protection.


v1.3.4 — Nginx FastCGI Cache Hygiene Edition

New FastCGI Cache Hygiene Engine

Added a new diagnostic system that detects broken, incomplete and orphaned FastCGI cache configurations.

Turbo Manager now correlates:

  • active CWP accounts;
  • /home directories;
  • configured Nginx virtual hosts;
  • FastCGI cache zones;
  • /etc/nginx/fastcgi-cache-sites/ files;
  • Nginx cache references;
  • active domain configuration.

This makes it possible to detect cases where a website or CWP account has been deleted but its old FastCGI cache configuration remains behind.

These stale entries can cause:

nginx -t

to fail even though Nginx itself is still running using its previously loaded configuration.

Orphaned Cache Detection

Turbo can now identify situations such as:

Domain removed
CWP account removed
/home account directory missing
Nginx vhost removed
FastCGI cache zone still present

Instead of showing only a generic Nginx failure, Turbo can classify the problem as an:

ORPHANED REMOVED SITE

and identify the affected domain, zone and stale configuration.

Safe Cache Cleanup

For confirmed orphaned cache configurations Turbo can offer:

Preview Safe Cache Hygiene Repair

followed by:

Apply Reviewed Cache Hygiene Repair

The repair workflow:

  1. identifies the exact configuration entries involved;
  2. backs up every file that may be changed;
  3. removes only the reviewed orphaned cache configuration;
  4. executes nginx -t;
  5. reloads Nginx only if validation succeeds;
  6. automatically restores the previous configuration if validation or reload fails.

Missing Cache Include Recovery

Turbo can also detect an active Nginx vhost referencing a missing file such as:

/etc/nginx/fastcgi-cache-sites/example.com.cache.conf

If exactly one existing FastCGI cache zone proves what the missing include must contain, Turbo can safely reconstruct it.

Example:

fastcgi_cache FCGI_EXAMPLE_COM;

Ambiguous or potentially dangerous situations remain review-only.

Active Site Protection

Turbo intentionally does not automatically recreate arbitrary /home directories or cache structures when ownership or account state is uncertain.

Active-site problems that cannot be repaired with strong evidence are clearly flagged for administrator review.

Better Nginx Evidence Refresh

After a reviewed Nginx repair, Turbo performs a targeted Nginx evidence refresh.

The GUI can therefore immediately change from:

Nginx syntax: FAILED

a:

Nginx syntax: VALID

without waiting for another deep audit.

Real-World Problem Covered

This release specifically protects against common CWP cleanup leftovers where a removed alojamiento account leaves behind a line such as:

fastcgi_cache_path /home/olduser/.nginx-cache/example.com ...

which would otherwise prevent future Nginx reloads or restarts.


v1.3.3 — Managed Update Reliability & Transactional Rollback Edition

Fixed Turbo Self-Update Failure

Corrected an important process-chain issue that could cause Turbo Manager to terminate its own update controller while performing a managed update.

This could previously result in confusing messages such as:

Action failed: Action completed.

even though the downloaded release itself was valid.

The installer now correctly protects the entire active updater process chain.

Transactional Managed Updates

Turbo Manager updates now follow a much stronger transactional workflow inspired by the mature CWP7 Tweak Manager updater.

Before changing the live installation Turbo now performs:

  1. licensed update authorization;
  2. signed release verification;
  3. package integrity validation;
  4. candidate installer preflight;
  5. pre-update backup;
  6. normal package installation;
  7. post-install version verification;
  8. Python validation;
  9. PHP GUI syntax validation;
  10. timer/service verification;
  11. automatic rollback if the update does not pass health verification.

install.sh --check

Release packages now support a safe preflight mode:

bash install.sh --check

This validates the candidate release without changing the installed Turbo Manager.

Root-Only Update Backups

Managed updates create protected backups under:

/root/cwp7-turbo-manager-update-backups/

The backup can include:

  • Turbo Manager backend files;
  • CWP GUI module files;
  • systemd units;
  • timer state;
  • important updater state.

Automatic Rollback

If an installation or post-install verification fails, Turbo attempts to restore:

  • previous program files;
  • GUI files;
  • systemd definitions;
  • previous timer enablement state.

Better Failure Reporting

Controller failures now return meaningful errors instead of generic messages such as:

Action completed.

v1.3.2 — Automatic Unattended Signed Updates Edition

Optional Automatic Updates

Added an administrator-controlled option to automatically install eligible future Turbo Manager releases.

Automatic updates are:

OFF by default.

The administrator can enable them from:

Turbo Manager → Updates

and select:

  • Stable channel;
  • Beta channel.

License Manager Controlled Rollout

Automatic installations respect the central Freespirits Software Release policy.

A release can specify:

  • servidor rollout percentage;
  • automatic-update delay;
  • whether automatic installation is allowed;
  • minimum supported client version;
  • Stable/Beta channel;
  • security/mandatory override policy.

Example:

Automatic update delay: 12 hours
Servidor rollout: 100%
Allow automatic installation: YES

Manual installation can remain available before the unattended deployment window opens.

Dedicated Update Timer

Added:

cwp-turbo-update.timer
cwp-turbo-update.service

The updater checks periodically with randomized scheduling to avoid having every licensed servidor contact the release service simultaneously.

Root-Owned Update Policy

Local automatic-update preferences are stored privately and preserved through future upgrades.

Servidor Pressure Protection

Automatic updates can be deferred when Turbo detects high servidor pressure.

This prevents an unattended software upgrade from competing with a heavily loaded production servidor.

Update Locking

Automatic updates share Turbo Manager’s background locking system.

An update will therefore not compete with another Turbo background job, audit or verification process.

Retry Protection

A failed unattended release is placed into a cooldown before Turbo attempts the same automatic installation again.

Manual administrator installation remains available.


v1.3.1 — PHP-FPM Saturation Detection Fix

Fixed False PHP-FPM Saturation Detection

Earlier logic could interpret:

4 PHP-FPM children
pm.max_children = 4

as:

PHP-FPM saturated 4/4

even though the four child processes could actually be idle.

Turbo Manager no longer treats the number of living PHP-FPM child processes as proof that a pool is busy.

Improved Pressure Evidence

Turbo now uses stronger runtime indicators such as request queue pressure where available.

A PHP-FPM pool is not classified as saturated simply because it has reached its configured number of spawned children.

Full Audit No Longer Aborts for One Busy Site

Previously one website with a temporarily busy PHP-FPM pool could terminate the complete Full Servidor Audit.

Turbo now allows the audit to continue.

A temporarily unavailable website can instead be reported as:

SKIPPED — temporarily busy

while remaining websites are still tested.

Conservative Retry Logic

Safety-sensitive website probes can perform bounded retry checks before deciding that a PHP-FPM pool should be deferred.

This reduces false rollbacks caused by momentary traffic bursts.

Better Audit Coverage Reporting

Turbo can now distinguish between:

  • tested websites;
  • successfully tested websites;
  • deferred websites;
  • failed websites.

v1.3.0 — Managed Software Updates Edition

Private Signed Software Updates

Introduced the Updates tab and integration with the Freespirits License Manager Software Releases service.

Turbo Manager can securely discover newer licensed releases without exposing permanent public download URLs.

Signed Release Verification

Before trusting a release Turbo verifies the Freespirits Ed25519 signed manifest.

The updater validates:

  • product identifier;
  • target version;
  • release ID;
  • package byte size;
  • SHA-256;
  • signing identity.

Pinned Signing Identity

Turbo Manager verifies the Freespirits release signing key against the expected fingerprint instead of blindly trusting any key returned by the servidor.

Private Licensed Downloads

Packages are downloaded using short-lived authorization tied to the active servidor license.

The full software license key is not exposed in normal command-line process arguments.

ZIP Security Inspection

Before installation Turbo rejects dangerous release packages containing conditions such as:

  • absolute filesystem paths;
  • ../ path traversal;
  • symbolic-link entries;
  • abnormal entry counts;
  • suspicious expanded package sizes;
  • unexpected release layout.

Managed Update Entitlement

Software licensing and software-update entitlement are treated separately.

A valid perpetual/lifetime software license can continue operating even when its included update period has ended.

Only access to newer managed releases is affected.

Included Update Period

Turbo Manager supports the commercial policy of a defined managed-update period from the first successful license activation.

Deactivation, reinstallation, transfer or reactivation does not reset the original update-entitlement start date.

Internal Servidor Ayuda

Servers designated as internal Freespirits systems can support unlimited managed update access while still requiring a valid Turbo Manager license.


v1.2.4 — License Deactivation Emergency Alerts

License Monitoring

Emergency Alerts can now notify administrators when the Turbo Manager commercial license becomes:

  • remotely deactivated;
  • denied;
  • invalid;
  • unusable after offline grace expires.

Multiple Email Recipients

License alerts use the Emergency Alerts recipient system and can notify multiple administrator email addresses.

Recovery Notifications

When enabled, Turbo can send a recovery notification after a license becomes healthy again.

False Alarm Protection

Temporary License Manager communication problems do not generate deactivation alerts while the signed offline license grace remains valid.

Fresh servers that have never been activated are also excluded from false deactivation notifications.

Privacy Protection

License-alert emails contain only masked license information and never expose the complete license key.


v1.2.3 — Targeted PHP State Refresh Fix

Fixed Stale PHP GUI Evidence

Corrected a state-refresh issue where administrator actions could succeed but the GUI immediately redisplayed older passive evidence.

This could previously create confusing combinations such as:

PHP runtime preflight is already healthy

while the same row still displayed:

REPAIR AVAILABLE
TUNE LOCKED

Targeted Deep Refresh

Administrator-requested PHP actions can now refresh the selected PHP version immediately.

This includes:

  • Retry Live Check;
  • Diagnose Runtime;
  • Repair Safe Issues;
  • Preview Tune;
  • Apply Preset;
  • Warm Verify;
  • OPcache-related administrator actions.

Low-Impact Background Architecture Preserved

Only the administrator-selected PHP target receives deep refresh work.

Scheduled passive scans remain lightweight.


v1.2.1 — Background Safety & Timer Hardening

Safer Background Architecture

Turbo’s scheduled monitoring was redesigned around the principle:

Automatic background work must remain lightweight and must not behave like synthetic customer traffic.

Zero Scheduled Customer-Site HTTP Probes

Passive scheduled scans avoid dynamic frontend website probes.

Deep website testing remains available through explicit administrator actions.

Background Mutual Exclusion

Turbo jobs use locking to prevent multiple background tasks from competing with one another.

Pressure-Aware Deferral

Scheduled work can be deferred when the servidor is under significant pressure.

Improved Timer Scheduling

Background timers use activation-relative scheduling so updates do not leave enabled timers with no future execution time.

Safer Temporary Files

Runtime state writes were hardened to avoid shared predictable temporary-file collisions between simultaneous actions.

Reduced Recurring Diagnostic Cost

Expensive PHP/Nginx diagnostic operations were moved away from frequent passive scans and reserved for explicit or less-frequent deep inspections.


v1.2.0 — LOW IMPACT / SAFE Architecture

Introduced Turbo Manager’s production-oriented passive monitoring model.

Scheduled scans became designed around:

  • cached deep evidence;
  • local process/service state;
  • lightweight system-resource checks;
  • no automatic browser benchmarks;
  • no recurring dynamic customer-site testing;
  • no unnecessary SQL runtime workload.

Turbo began clearly separating:

Scheduled passive monitoring

from:

Administrator-requested deep diagnostics

and:

Manual performance testing


Current Safety Philosophy

Modern Turbo Manager uses several layers of protection before changing production configuration.

Depending on the feature, these can include:

  • Preview before Apply;
  • administrator confirmation;
  • current-configuration validation;
  • backup creation;
  • service-specific preflight;
  • syntax validation;
  • graceful reload;
  • post-change verification;
  • website regression testing;
  • automatic rollback;
  • scheduled follow-up checks;
  • servidor-pressure awareness;
  • managed license validation;
  • signed update verification.

Turbo Manager deliberately refuses to optimize when the existing servidor configuration is already unsafe.

For example, an Nginx optimization may be marked:

ALREADY SAFE

while Apply remains blocked because:

nginx -t is not currently valid

This means the requested optimization itself is correct, but Turbo detected another servidor configuration problem and refused to make additional changes until it was resolved.


Major Turbo Manager Capabilities

Current releases provide a unified CWP7 interface for:

Servidor Auditing
Review CPU, memory, swap, services, PHP, database, Nginx and hosted-site performance evidence.

PHP-FPM & OPcache Analysis
Map real HTTP/HTTPS vhosts to CWP alternate PHP versions and measure live OPcache state before recommending changes.

Smart OPcache Tuning
Identify memory pressure, interned-string pressure and OPcache key-table exhaustion and produce reviewed tuning recommendations.

Nginx FastCGI Cache Safety
Inspect cache configuration, query-string behavior, original-path handling and cache-key collision risks.

FastCGI Cache Hygiene
Detect orphaned cache zones, stale configuration belonging to removed sites and missing active cache includes.

Website Testing
Perform administrator-requested website probes with safety controls and bounded failure handling.

Performance Lab
Investigate frontend performance, dependencies and browser-visible bottlenecks.

Safe Performance Presets
Preview, apply, validate and automatically roll back supported servidor optimizations.

Scheduled Post-Tune Verification
Monitor important configuration changes after application instead of assuming that a successful reload guarantees long-term correctness.

Emergency Alerts
Notify multiple administrators about selected important runtime or licensing problems.

Commercial Licensing
Bind licensed installations to supported servers while maintaining offline grace and state-aware licensing behavior.

Private Managed Updates
Receive authorized releases through the Freespirits Software Release infrastructure with cryptographic verification.

Optional Unattended Updates
Automatically deploy approved new releases while respecting release channel, entitlement, publisher delay, rollout percentage and servidor-pressure safeguards.


Upgrade Recommendation

For production systems, always keep Turbo Manager on the newest Stable release available to your licensed servidor.

From v1.3.x onward, the integrated Updates tab can securely discover newer entitled versions.

From v1.3.2 onward, administrators can optionally enable automatic unattended updates.

From v1.3.3 onward, managed updates benefit from the strengthened transactional backup, verification and rollback workflow.

Latest release: CWP7 Turbo Manager v1.3.4

Latest Changes

v1.3.8

Bugfix

What's fixed
CWP7 Turbo Manager v1.3.8 fixes a v1.3.7 runtime regression where Preview Tune could fail with name 'round_up_step' is not defined whenever OPcache memory pressure required Turbo to calculate a larger memory allocation. The missing rounding helper has been restored and the recommendation branch is now covered by an actual runtime regression test rather than syntax checks alone. The failed Preview action was read-only and did not modify PHP configuration or reload/restart PHP-FPM.
This release also fixes the older latent nginx_details is not defined error in scheduled Nginx follow-ups. The restored helper remains strictly low-impact and reuses cached/local Nginx evidence without running deep Nginx tests or customer-site probes.
All v1.3.7 shared PHP-FPM/OPcache protections, read-only Live Check behavior, rollback safeguards, PHP 8.5 compatibility, RAM-aware OPcache tuning, Full Audit live checks for all installed PHP versions, Nginx cache hygiene, licensing and unattended-update functionality are preserved.

v1.3.7

Minor

What's fixed

CWP7 Turbo Manager v1.3.7 significantly hardens PHP-FPM and OPcache safety for shared CWP7 hosting environments. Live OPcache diagnostics are now strictly read-only and no longer create temporary PHP files in customer websites, reset or invalidate OPcache, change configuration, or reload/restart PHP-FPM. Turbo now detects cross-account shared-OPcache risks, PHP-FPM worker exit code 70, Cannot kill process … Operation not permitted, forced-restart lock conflicts, Nginx FastCGI record failures and related 502 evidence. Legacy PHP 7.4-or-older services shared by multiple Unix account users with an active opcache.force_restart_timeout are automatically protected from OPcache Apply/reload operations. Fresh pre-change safety validation is performed before any configuration write, while post-change verification detects newly introduced PHP-FPM/FastCGI failures and automatically restores the exact previous configuration if necessary. Full Server Audit continues to refresh live OPcache for every installed PHP version, now using the new local read-only direct-FPM probe. All existing Turbo Manager settings, licensing, unattended updates, PHP 8.5 compatibility, Nginx cache hygiene and previous performance functionality are preserved.

v1.3.6

Bugfix

- active PHP versions used by websites get a fresh live OPcache measurement;
- unused PHP versions are refreshed as UNUSED / Not applicable;
- inactive versions are clearly marked unmeasured;
- the PHP / OPcache page immediately uses the fresh values;
- you no longer need to press Retry Live Check separately for PHP 7.4, 8.3, 8.5, etc.
The scheduled passive scan is unchanged and still avoids PHP binaries and website probes.