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

API RPC Protocol problems

L

lazolie

New Pleskian
Hi,

we have installed the current 10.4.4 Version of Plesk on a Virtual Server. By using the the API we got the error:

Protocol version '1.6.3.4' is not supported. Current protocol version is '1.6.0.2'

The Documentation said that the 10.4.4. should have the version 1.6.3.4!

Do you have any idea?
 
Are you sure that you have installed psa-api-rpc package for 10.x version?
What sort of output following command:

# rpm -qi psa-api-rpc

?
 
Yes, i am sure:

# dpkg -l | grep psa-api-rpc
ii psa-api-rpc 10.0.0-1 Transitional package for psa-api-rpc

What is wrong?
 
You must log in or register to reply here.

Similar threads

P
Issue HTTP3 does not work in NGINX only server
Replies
10
Views
3K
learning_curve
learning_curve
S
Issue GetDatabases Rest API Fatal Error
Replies
2
Views
467
Kaspar
K
Lexz
Resolved 'CP User Login Attempt via API Failed' ('Login Name': '<invalid>' => '')
Replies
3
Views
1K
Lexz
Lexz
E
Issue Plesk API / Commands
Replies
1
Views
580
Kaspar
K
NateWon
Question Composer and default PHP version
Replies
1
Views
327
Kaspar
K
Back
Top