• 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.

Question Removed PHP 8.0 from the server but a single version still be linked with an warning or error message, why?

PeopleInside

Regular Pleskian
Server operating system version
Ubuntu 22.04.1 LTS
Plesk version and microupdate number
18.0.48, last updated on Dec 14, 2022 11:19 PM
Hi, I removed PHP 8.0 from Plesk.

Why I see this warning and PHP 8.0 still listed?
Thanks

1673360800386.png
 
Hi, I removed PHP 8.0 from Plesk.

Why I see this warning and PHP 8.0 still listed?
Thanks
~~~
Out of interest, do you run Roundcube?
If you look at this thread: Question - Plesk Obsidian and PHP 8 compatibility
You'll see, that with effect from Plesk Obsidian 18.0.49, Roundcube runs on PHP 8.0. So ...IF... you fall into the criterea that's covered in that thread, then that might be a cause of the issue that you've experienced. From our own past experience, we had a similar error (but on earlier PHP and Roundcube releases).
 
Back
Top