Apache Modules
Apache Modules lets ROOT turn Apache's modules on and off, safely. Modules are grouped by category with plain descriptions, the ones the platform depends on are locked so they cannot be disabled by accident, dependencies are checked both ways, and changes are batched and applied with a syntax test and automatic rollback.
Web Server → Apache Moduleshttps://YOUR-SERVER-IP:8443/webserver/apache-modules (apply: ROOT)The module list
Every module Apache actually has on disk is listed, grouped into categories (Proxy, Security, Performance, Cache, Authentication, URL Rewriting and more), each with a one-line description of what it does. Search by name or description, filter by state (enabled, disabled, locked), and the four cards up top count the totals at a glance. Two reference cards suggest the modules most servers want enabled and the security-related ones.
Enabling and disabling
Flip a module's switch and the change is staged, not applied immediately: you build up a batch of changes, review them in a banner, and then Apply & Restart them together. Toggling a module twice cancels the pending change.
a2enmod. Instead the panel comments or uncomments the LoadModule line directly in Apache's config. Applying a batch backs up the config, makes the edits, runs apachectl -t to check the syntax, then reloads Apache gracefully (draining in-flight requests). If the test or reload fails, everything is rolled back to the previous config and reloaded, so the change set is all-or-nothing and never leaves Apache broken.Protected modules and dependencies
Seventeen modules are locked: they cannot be disabled because the Panelica stack needs them, and each says why.
| Locked module | Why it is required |
|---|---|
| mod_proxy, mod_proxy_fcgi | Connect Apache to PHP-FPM |
| mod_remoteip | Recover the real visitor IP from Nginx in front |
| mod_ssl, mod_socache_shmcb | HTTPS and its session cache |
| mod_security2, mod_unique_id | The Web Application Firewall |
| mod_rewrite, mod_dir | .htaccess rewrites and directory index |
| mod_suexec, mod_unixd | Per-user isolation and Apache's user/group |
| mod_authz_core, mod_authn_core, mod_reqtimeout, mod_mime, mod_log_config, mod_version | Core access control, request-timeout safety, MIME types, logging, versioned config |
Beyond the locks, dependencies are enforced both directions: the panel warns you (and the backend refuses) if you try to enable a module whose prerequisite is off, or disable one that another active module depends on. That is what stops you from, say, disabling mod_proxy and silently breaking PHP on every site.
.htaccess; the unlocked ones you can safely toggle rarely move the needle on memory. If memory is the goal, the lever is the Apache MPM on the Web Server Settings page, not the module list.Access
Viewing the module list is open to ROOT and ADMIN (with the webserver.apache-modules page permission), but applying changes is strictly ROOT (enforced at the backend; an admin sees the list but gets a notice instead of the Apply button). See roles and permissions. Everything operates on Panelica's isolated Apache under /opt/panelica, never the system Apache.