• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Selecting Third-Party Services

S

sfogonline

Guest
After logging into my server, I receive a page prompting me to select "Third-Party Services". I select everything and after clicking ok get the following message:

"Some service categories contain invalid selections, or no selections were made."

Even though selections are available, it highlights the following:

- component_name__backupsystem.acronis
- component_name__database.mssql
- component_name__database.mysql
- FTP Server
- component_name__java.jdk
- component_name__java.tomcat
- component_name__network.qos
- component_name__psa.core
- component_name__script.asp
- component_name__script.asp.net
- component_name__script.perl
- component_name__script.php
- component_name__script.python
- component_name__script.ssi
- component_name__sqladmin.mssql
- component_name__sqladmin.mysql
- component_name__stats.awstats
- component_name__stats.smarterstats
- component_name__stats.urchin
- component_name__stats.webalizer
- component_name__webpublish.fp

I've tried checking "none" and the software available under the different titles, but nothing removes them from the list.

Regards,

Nick Caughman
 
open a support ticket. we need to hammer them with tickets :)

I think I have 5 to open today alone with issues that have arised after i installed the 7.5.1 hotfix on a beta server.
 
I've got the same problem here as well. What gives on this thing? I paid $200 for Plesk and I can't get it off the ground...
 
Have the folks at Plesk said anything about what's causing this error or how to get around it? It's driving me up the wall.

I have 2 support emails and a phone call pending with them and it's a bit frustrating.
 
Back
Top