• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

API problems after upgrade to 8.1.1

O

oschost

Guest
Hello,

I've got a problem talking to the api. This was working fine (with packet version 1.4.2.0 before upgrading to 8.1.1) now what ever packet version I send I get the result at the bottom of the post :-(


I try and send the standard

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<packet version="1.5.0.0">
<client>
<add>
<gen_info>
<cname>LogicSoft Ltd.</cname>
<pname>Stephen Lowell</pname>
<login>stevelow</login>
<passwd>steve78</passwd>
<status>0</status>
<phone>416 907 9944</phone>
<fax>928 752 3905</fax>
<email>[email protected]</email>
<address>105 Brisbane Road, Unit 2</address>
<city>Toronto</city>
<state/>
<pcode/>
<country>CA</country>
</gen_info>
<limits>
<disk_space>100000</disk_space>
<max_dom>50</max_dom>
<max_subdom>250</max_subdom>
<max_webapps>30</max_webapps>
<max_traffic>50000</max_traffic>
<max_db>200</max_db>
<mysql_dbase_space>50000</mysql_dbase_space>
<max_shared_ssl_links>50</max_shared_ssl_links>
<expiration>1134616208</expiration>
</limits>
<permissions>
<create_domains>true</create_domains>
<manage_phosting>true</manage_phosting>
<manage_quota>false</manage_quota>
<manage_subdomains>true</manage_subdomains>
<change_limits>true</change_limits>
<manage_dns>true</manage_dns>
<manage_log>true</manage_log>
<manage_anonftp>true</manage_anonftp>
<manage_webapps>true</manage_webapps>
<manage_sh_access>true</manage_sh_access>
<manage_maillists>true</manage_maillists>
<make_dumps>true</make_dumps>
<remote_access_interface>true</remote_access_interface>
<cp_access>true</cp_access>
<manage_domain_aliases>true </manage_domain_aliases>
</permissions>
</add>
</client>
</packet>


and the response I get is:

<?xml version="1.0"?>
<packet version="0.0.0.0">
<system>
<status>error</status>
<errcode>1005</errcode>
<errtext>Protocol version '0.0.0.0' is not supported. Current protocol version is '1.5.0.0'</errtext>
</system> </packet>


Please if anyone knows how to fix this let me know :) it's driving me insane!

Matt
 
Disappointingly I contact SWSoft support - and they require me to take out a support contact. Big shame that - as upgrades that break functionality should be supported.

Perhaps after a year and a half of Plesk life I should start looking at other control panels.

Very VERY disappointed...........
 
One thing to note is that using the 1.5.0.0 packet schema, limits, permissions and hosting attributes have changed.

They must be in the format (same with <permissions>..</permissions>):

Code:
<limits>
  <limit>
     <name>max_subdom</name>
     <value>2</value>
  </limit>
  <limit>
     <name>disk_space</name>
     <value>1024</value>
  </limit>
</limits>

To get a list of limits/permissions, and their corresponding data types use the following;

Code:
<packet version='1.5.0.0'>
 <domain>
  <get-permission-descriptor>
   <filter>
    <id>13</id>
   </filter>
  </get-permission-descriptor>
  <get-physical-hosting-descriptor>
   <filter>
    <id>13</id>
   </filter>
  </get-physical-hosting-descriptor>
 </domain>
<packet>

API documentation, including the changes are here: http://download1.swsoft.com/Plesk/Plesk8.1/Doc/plesk-8.1-api-rpc/index.htm
 
I have somewhat the same problem.
Using plesk 8.1.1 on linux.

As per the following document:
http://download1.swsoft.com/Plesk/Plesk8.1/Doc/plesk-8.1-api-rpc/36172.htm

I am sending the following:
Code:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<packet version="1.4.2.0">
<server>
<get_protos />
</server>

</packet>

and I get the following back:

Code:
<?xml version="1.0"?>
        <packet version="0.0.0.0">
                <system>
                        <status>error</status>
                        <errcode>1005</errcode>
                        <errtext>Protocol version '0.0.0.0' is not supported. Current protocol version is '1.4.2.0'</errtext>
                </system>       </packet>

It works fine on my plesk which I have a support contract, but not on another one which got installed by the provider (included in the price) but without support contract. So I cannot contact plesk about my second plesk since I have no support contract with them for the plesk I have a problem with :(

I noticed that both plesk had different version so I upgraded the oldest and I still get the error.

I tried using version 1.5.0.0 but same effect.

I was not able to identify anything else different that might explain this problem. Any help would be appreciated.
 
I found the problem.
The plesk admin password had a newline in it. The HTTP header was therefor broken.

Now it is working fine.
 
Originally posted by infiniweb
I found the problem.
The plesk admin password had a newline in it. The HTTP header was therefor broken.

Now it is working fine.

How did you solve it? I have the same problem.
 
I simply removed the newline in the password. Make sure this is what is causing your problem.
Maybe your problem is caused by something else.
 
Originally posted by infiniweb
I simply removed the newline in the password. Make sure this is what is causing your problem.
Maybe your problem is caused by something else.

This is not my problem :(
 
Back
Top