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

Issue Plesk Wordpress Clone Target Existing Domain Issue

first4it

New Pleskian
Server operating system version
AlmaLinux 9.7
Plesk version and microupdate number
Plesk Obsidian 18.0.74 Update #3
This is a strange issue and the behaviour is weird. I have created a subdomain of one of my existing sites in Plesk using the subdomain prefix stage i.e. stage.mydomain.com.

If I select the Wordpress Clone option from the menu, click on the source website of mydomain.com and then in the target, select existing site. The drop-down list shows me all of the sub domains on the server, including stage.mydomain.com. If I try to select stage.mydomain.com, the list box reverts to mydomain.com. I have one or two other sub domains for other domains listed and I can select one of these but no the other.

I cannot currently clone from live to staging for this site.

Does anyone have any ideas if this is a bug?
 
Hello, @first4it . Do you have anything deployed under stage.mydomain.com, e.g. an existing clone? I am unable to replicate the issue on a test environment. The website is successfully cloned under stage.mydomain.com when I try. Please provide us with more details - what's the document root of the subdomain; is there any content under the directory before you attempt to clone, a screenshot of what you see exactly.
Thanks in advance.
 

Attachments

  • Screenshot 2026-01-08 183001.png
    Screenshot 2026-01-08 183001.png
    49.5 KB · Views: 3
Back
Top