• 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

Resolved Can't Install Slave DNS Manager

Ladylinux

New Pleskian
Server operating system version
Debian 11.6 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.52.0
Hi,

Fresh Debian 11 install with Plesk 18.0.52

I get this when I try to install Slave Dns Manager from either the GUI or via command line

"
plesk bin extension --install slave-dns-manager
[2023-04-27 01:35:12.421] 2689:644944aaaee43 ERR [extension/slave-dns-manager] The execution of post-install.php has failed with the following message:
Execution server_dns has failed with exit code 1, stdout: , stderr: [2023-04-27 01:35:12.397] 2786:644944b060d69 ERR [panel] Custom DNS backend has finished with a non-zero error code 1, stderr: [2023-04-27 01:35:12.390] 2821:644944b05ef6b ERR [extension/slave-dns-manager] The execution of slave-dns.php has failed with the following message:
Invalid json data input:
The execution of slave-dns.php has failed with the following message:
Invalid json data input:


Unable to enable Custom DNS backend: invalid DNS backend script.



The execution of post-install.php has failed with the following message:
Execution server_dns has failed with exit code 1, stdout: , stderr: [2023-04-27 01:35:12.397] 2786:644944b060d69 ERR [panel] Custom DNS backend has finished with a non-zero error code 1, stderr: [2023-04-27 01:35:12.390] 2821:644944b05ef6b ERR [extension/slave-dns-manager] The execution of slave-dns.php has failed with the following message:
Invalid json data input:
The execution of slave-dns.php has failed with the following message:
Invalid json data input:


Unable to enable Custom DNS backend: invalid DNS backend script.




exit status 1"

I went to a secondary Debian 11 server to see if it was just this server but I was able to easily install the Extension there.

Thanks!!

LadyLinux
 
It's a brand new issue that was discovered here, too around the time when you posted. It has already been escalated and a fix has already been prepared. It will be published very soon.
 
Hello,

OK I was able to enable the extension after implementing the patch.

Reinstalling it threw the same errors as expected but once I patched that file it appears to be operating properly :)

Thanks Again!!

LadyLinux
 
Back
Top