• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by J8643

  1. J

    Resolved API RPC - Creating Subscription Error

    Hi IgorG, I tried running plesk repiar db and plesk db repair But it doesn't look like those commands work with the plesk automation management node. Error message below. [root@ppa ~]# plesk repiar db Usage: plesk db [command|sql] Execute database specific command. Open MySQL console if...
  2. J

    Resolved API RPC - Creating Subscription Error

    Hi Igor, An update on this, it turns out even when it returns the "Operation in POA failed: [no error code] Unable to find the webspace with ID 0." error, it is still creating the website in plesk, it just isn't associating any hosting with it (despite me specifying hosting now).
  3. J

    Resolved API RPC - Creating Subscription Error

    Hi Igor, I've added the following below the gen_setup node but am still getting the same result: <hosting> <vrt_hst> <property> <name>ftp_login</name> <value>{login}</value> </property> <property> <name>ftp_password</name>...
  4. J

    Resolved API RPC - Creating Subscription Error

    Hi, I'm having trouble creating a new subscription on the plesk api. Below is the packet format I'm sending: <packet version="1.6.5.0"> <webspace> <add> <gen_setup> <name>example.co.uk</name> <owner-id>{ownerid}</owner-id> <owner-login>{owner}</owner-login> <ip_address>{iphere}</ip_address>...
  5. J

    API RPC - Creating Subscription Error

    Hi, I'm having trouble creating a new subscription on the plesk api. Below is the packet format I'm sending: <packet version="1.6.5.0"> <webspace> <add> <gen_setup> <name>example.co.uk</name> <owner-id>{ownerid}</owner-id> <owner-login>{owner}</owner-login>...
Back
Top