• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved PHP FPM 8.2 service Not configured

pulsarinformatique

New Pleskian
Server operating system version
Debian 11.7
Plesk version and microupdate number
18.0.52 update 3
Hi
Why a fresh Obsidian install with all the available PHP version installed, we still have the message "Not configured" for PHP-FPM 8.2.6 in the /admin/services/list ?
What did we forget please?

thanks

Cyril
 
The service is configured and started only after at least one domain is configured to use PHP-FPM 8.2.6.
 
This is one of the most misunderstood issues in Plesk.

The text should read: "Not used" or "Not in use" instead of "Not configured"
I agree. The current status indication is confusing. Obviously this isn't really a bug, but it doesn't feel like a feature improvement either. @Peter Debik what would be the best way to get this on Plesk's radar?
 
We'll have a look at it, at least I have forwarded it.

Technically, "not configured" is correct, because the .conf file does not exist and when no such .conf files exist in the PHP configuration file directory, a service start will fail. But I, too, remember several discussions here where the "not configured" was confusing.
 
Back
Top