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

Plesk 12.5 API webspace gen_info status 1

SBurina

New Pleskian
Hi!

I'm getting an undocumented status code "1" from API call to get a subscription (webspace) genral info:

Code:
PleskX\Api\XmlResponse {#829
  +"status": "ok"
  +"filter-id": "example.com"
  +"id": "70"
  +"data": PleskX\Api\XmlResponse {#835
    +"gen_info": PleskX\Api\XmlResponse {#837
      +"cr_date": "2015-05-11"
      +"name": "example.com"
      +"ascii-name": "example.com"
      +"status": "1"
      +"real_size": "5275648"
      +"owner-id": "58"
      +"dns_ip_address": "XX.XX.XX.XX"
      +"htype": "vrt_hst"
      +"guid": "3602b687-c1fe-4b88-9983-405f739a3558"
      +"vendor-guid": "6fdec3be-c2ee-4186-bc9b-3c1fd31a1af1"
      +"external-id": PleskX\Api\XmlResponse {#839}
      +"sb-site-uuid": PleskX\Api\XmlResponse {#840}
      +"description": PleskX\Api\XmlResponse {#841}
      +"admin-description": PleskX\Api\XmlResponse {#842}
    }
  }
}

As far as I could understand, the codes should be 0, 16, 32, 64, and 128.
Is this normal or I'm doing something wrong?

Thank you!
 
Looks like status code 1 means 'suspended' - https://kb.plesk.com/en/127156

Hi, Igor!

Thanks for the link. There are some status codes missing in the API docs, or I couldn't find that part. But, still, the subscription was suspended by admin, not by user. So why is it 1 instead of 16? Hmm..
I suspended the subscription from the command line, using the command "plesk bin subscription --webspace-off <domain.tld>". It seems that this command set the status 1. I'll try to suspend it through API and see if there's a difference - I guess it will be OK, since the API call explicitly states the status 16.

Thank you once again for your swift response! :)
 
Back
Top