Issue Wordpress installation failed (Plesk for Windows)

[Brovning]

Server operating system version

Windows

Plesk version and microupdate number

18.0.58

Hello,

I'm trying to install Wordpress with:
PLESK 18.x for WINDOWS
PHP 7.4

I'm starting the installation in customer panel:


Afterwards the installation is running:


After some time the following page is opened:



How can I identify the rootcause?

 

[Brovning]

I have tried to install Wordpress with the "WP Toolkit":

Error message:
"Unable to unpack archive C:\Inetpub\vhosts\***\httpdocs\wp67cc98d30fa4c8.41816230\wordpress-6.7.2.zip to C:\Inetpub\vhosts\***\httpdocs\wp67cc98d30fa4c8.41816230 at (UnpackArchive:: onRunAsUser line 2832) at Unable to unpack archive C:\Inetpub\vhosts\***\httpdocs\wp67cc98d30fa4c8.41816230\wordpress-6.7.2.zip(UnpackArchive:: onRunAsUser line 2835)"

Any ideas?

 

[Sebahat.hadzhi]

Hello, @Brovning . Could you please double-check the Hard Disk Quota set in Domains > example.com > Web Hosting and make sure it is not too low? If possible, please temporarily set it to unlimited for the sake of testing.

 

[Brovning]

Hello, @Brovning . Could you please double-check the Hard Disk Quota set in Domains > example.com > Web Hosting and make sure it is not too low? If possible, please temporarily set it to unlimited for the sake of testing.

Hello @Sebahat.hadzhi,

hard disk quota is set to unlimited.
I have tried it with another domain. There the installation finished successfully.

Difference:
sub.domain.com --> failed
domain.com --> success

Is it possible to install Wordpress using a subdomain as main domain for the account?

 

[Sebahat.hadzhi]

Thank you for the confirmation, @Brovning You should be able to install WordPress on a subdomain even if it's set as the primary one for the subscription. The root cause of the issue lays somewhere else. My other guess would be a permission issue. Could you please try running the Plesk repaid utility by executing the following command via RDP:

plesk repair fs

If that doesn't sort out the issue, I would recommend getting in touch with our support team for further investigation.