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

Symantec SSL ERROR API request responded with a 0 code.

Paulo Freitas

New Pleskian
TITLE:
Symantec SSL ERROR API request responded with a 0 code.
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
windows server 2012 r2 64bits
Plesk Onyx
Version 17.5.3
PROBLEM DESCRIPTION:
After i click activate i see this error

"Error: Something went wrong with your order. Please double check configuration parameters.API request responded with a 0 code."

what should i do??​
STEPS TO REPRODUCE:
when i try to active a symantec ssl in all the websites i see the same error​
ACTUAL RESULT:
Error: Something went wrong with your order. Please double check configuration parameters.API request responded with a 0 code.​
EXPECTED RESULT:
need to work​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out
 
Back
Top