• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Import WordPress Website: There were issues when transferring source folder

micheee

New Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
18.0.52.3
I am trying to import a website from another Hoster to our plesk instance, I am using:
Bash:
# plesk version
Product version: Plesk Obsidian 18.0.52.3
     OS version: Ubuntu 20.04 x86_64
     Build date: 2023/05/16 12:00
     Revision: a3b74dbc9de2e47afd4e532d02fa7759b29d3fa5


The connection can be established via SSH just fine, I can even browse folders on the remote server:

1684849774812.png

When I try to actually import, the following error is returned:
Code:
Executed command:
 scp -r -i /var/www/vhosts/new-somewhere/site-import-key \
   -P 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no \
   -o GSSAPIAuthentication=no \
   user@somewhere:/html/wordpress/. /var/www/vhosts/new-somewhere/httpdocs/
Output:
error: unexpected filename: .

It seems like scp, due to CVE-2018-20685 disallows the '.' that Plesk generates in the copy-command. Unfortunately, I am unable to change the scp on the receiving side.

I already attempted to set the source document to both "/home/user/html/wordpress/", "/home/user/html/wordpress" (instead of automatic detection) but it did not change the behavior.

I have a feeling that this used to work some time ago — but I can't remember exactly when this was.
 
Back
Top