• 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

Question Website copying does not work

olegos76

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
18.0.50 Update #2
Hello. Could you please help me with following problem?

Goal: create an exact copy/clone of the main website www.***.com (not WordPress) to dev.***.com for development/testing purposes.

The problem: I don't see a "clone" option anywhere at all, so I only tried using "Website copying". Selected the only option from -> to and said OK.

1678729653196.png


After 1 second I see notification "The website files were copied."
Checked: dev.***.com still has all of it's old files and clearly nothing was copied.

Am I doing something wrong?

Thank you very much!
 
That's strange, the copy option should work as intended (i.e copying all files from one domains document root to another domain document root). Any related messages in the Plesk error log? (Tools & Settings > Log browser > Plesk (tab)).
 
I cleared logs. Turned on "Real-time" and nothing. No logs coming in at all after copying. Just the message:
1678772099039.png
 
Did you verify that the path to the document root directory in "Hosting Settings" is the same where you are looking for the copied files? I am asking, because sometimes users name their document root different from their domain name, but leave the old path named after the domain name in place. So later they mix paths up. It is just a thought.
 
Did you verify that the path to the document root directory in "Hosting Settings" is the same where you are looking for the copied files? I am asking, because sometimes users name their document root different from their domain name, but leave the old path named after the domain name in place. So later they mix paths up. It is just a thought.
Thanks Peter, yes, verified:
Source website doc root: httpdocs/laravell/public
Destination subdomain doc root: dev.****.com/laravell/public
 
I am unable to replicate the issue on my server. For me all files (within the document root) are copied to another domain, even when a different document root has been set (on both source and target domain). As a workaround you could also use the Copy function of te File Manager to copy files over if both domain are in the same subscription/webspace. Which maybe is not as convenient as the dedicated copy feature, but it does the job.
Schermafbeelding 2023-03-14 170654.png

If really like to use the dedicated copy feature I suggest opening a support ticket so support engineers can investigate the issue directly on your server. For support see: https://www.plesk.com/kb/support/how-to-get-support-directly-from-plesk/
 
I noticed you are mentioning Laravel in your path.
I had the same issue when using the Website Copy feature for a Laravel application. Only the contents of the httpdocs/public folder were copied to the new location.

So I had to temporarily change the hosting path for the active Laravel website to the standard httpdocs only, perform the Website Copy, then change back to httpdocs/public.

Then all files were copied including subfolders.
Afterwards I could change the hosting path for the destination, containing the newly copied files, to httpdocs/public and scan for Laravel applications and voila, my copied application was found.

Hope this helps other searching for this because I did not find any documentation on how to effectively copy a laravel application using Plesk.
 
  • Like
Reactions: JVG
Back
Top