• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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