Question Plesk 18.0.74 and Debian 13

[manos]

Server operating system version

Debian 13.2

Plesk version and microupdate number

18.0.74 #2

Hello,

Using RHEL releases (mostly almalinux 9.7) at all our servers so far, at last one decided to check debian 13.

Everything seems to work fine, just a question to experienced at debian.

At apache settings of Plesk with debian 13 noticed that very few apache modules are enabled by default.

When tried to migrate some sites from plesk/almalinux servers got a warning for a bunch of not enabled or not installed apache modules at target (debian 13) plesk server.

Migrations gone through and sites seem to work fine so far.

Is there a list of recommended apache modules that need to be enabled for usual wordpress sites at this configuration?

Thanks

 

[Maarten]

Hi,

Could you share the specific warning messages from the migration? That will tell us exactly which modules it's looking for.

However, keep in mind that RHEL-based distros tend to enable many Apache modules by default that aren't strictly necessary. Debian takes a more minimal approach for security reasons.

Rather than blindly enabling all modules from the warning list, I'd recommend:
1. Test your WordPress sites thoroughly (especially image uploads, contact forms, caching)
2. Check your Apache error logs for any actual missing module errors
3. Only enable modules when you confirm they're actually needed

For typical WordPress sites, you usually need: rewrite, headers, expires, ssl, mime. But the exact list depends on your plugins and setup.

 

[manos]

Thank you so much for detailed reply!

>>>Could you share the specific warning messages from the migration? That will tell us exactly which modules it's looking for.

Sure will do asap

>>>However, keep in mind that RHEL-based distros tend to enable many Apache modules by default that aren't strictly necessary. Debian takes a more minimal >>approach for security reasons.

This is what i suspected as well!!!

>>Rather than blindly enabling all modules from the warning list, I'd recommend:
>>1. Test your WordPress sites thoroughly (especially image uploads, contact forms, caching)
>>2. Check your Apache error logs for any actual missing module errors
>>3. Only enable modules when you confirm they're actually needed

Yes, did 2 and 3 will check frontends manually


By the way as i enabled some modules i was thinking were needed, could someone share a screenshot with the initial
modules enabled/disabled from plesk with debian 13?

Thanks again

 

[manos]

Here are the warnings.
Checked all sites and work fine

The following Apache modules are not installed on the destination server: systemd. Please install and turn on these modules in Plesk to prevent some possible problems.

The following Apache modules are disabled on the destination server: http2, log_config, logio, lua, mime_magic, passenger, proxy_ajp, proxy_connect, proxy_express, proxy_fdpass, proxy_http2, unixd, version, watchdog.

 

[Maarten]

You can safely ignore most of the warnings.
The modules listed (like log_config, logio, lua, mime_magic, proxy_ajp, proxy_connect, proxy_express, proxy_fdpass, unixd, version, watchdog) aren’t important for normal Plesk hosting. They appear because they were enabled on your old RHEL server, while Debian ships with a smaller default set of Apache modules.

Regarding http2: Apache’s mod_http2 is not enabled by default on Debian, but in most Plesk setups, Nginx acts as the frontend proxy and already serves sites over HTTP/2. So even if Apache’s http2 module is missing, your sites can still use HTTP/2 without any issues.

If all your sites are working fine, there’s no need to enable any of these modules manually.