Unable to import site: Unable to locate the document root directory of the website

Follow

Comments

11 comments

  • Avatar
    Lenor

    I really don't understand this Tool. 

    This worked only once Plesk to Plesk. Nothing else. 

    No Strato, no 1und1 and Host Europe or ALL INKL. 

    Nothing. Regardless what Settings I set, i tried EVERYTHING. 

    Why do you have this Tool, how can it be used if not transfering Sites? ^^

    1
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Lenor,

    Hello!

    In case nothing helps, I suggest submitting a ticket to Plesk support to find the cause of the issue.

    0
    Comment actions Permalink
  • Avatar
    Lenor

    I tried this on several Serves, seems not working at all. There's a connection but nothing more. Second Step always fails.

    I am not direkt partnered with Plesk. 

    1
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Lenor,

    You may purchase a support subscription. The first month is for free.

    -1
    Comment actions Permalink
  • Avatar
    Brian Chin

    I was behind Cloudflare and changing the a record from proxied to dns only solved the problem.

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Brian Chin Thanks for sharing!

    0
    Comment actions Permalink
  • Avatar
    Eris

    I tried in all the maniers but gives me the same problem.I'm using prestashop 1.7.6.1 and doesn't work the resolution writed up. i didnt have a public_html and files are dierctly in /www.mysite.it

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Hi @Eris, Please make sure /www.mysite.it is set as Document root in Domains > example.com > Hosting Settings. If not could you please open a support ticket with us by following this guide https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-.

     

    0
    Comment actions Permalink
  • Avatar
    b_p (Edited )

    Julian Bonpland Mignaquy Ekaterina Babenko  this tool clearly needs to be reworked and the instructions need improvements (tested on 18.0.27):

    1. At least in the German translation, when you open the Import tool, the heading shows a link to "switch to simple mode" even though the simple mode is selected. If you follow the link, the advanced mode will be shown, but the link text always remains the same.
    2. The wording source domain name is misleading. If transferring a domain "example.com", I would assume that I need to enter this domain name here. However, it turns out that you refer to the source (FTP/SSH) host name here. This is not clear at all and needs to be fixed. Especially with commercial hosting companies, the FTP server name is often completely different to the actual domain name.
    3. In my case, I tried to import a website from a server where the (virtual) root directory for the FTP server does not coincide with the actual server root directory (and where the HTTP docroot is a subdirectory of that virtual root (e.g. /example.com where the actual path name in the server file system would be /var/www/clients/clientXY/example.com). I interpreted the instructions of the import tool such that in this case, I would need to set the "source document root" to "/example.com". Instead, I actually had to provide this as "files root". This is completely misleading. So please improve the descriptions (and do so without asking me to file a request on uservoice.com! This is a clear usability BUG and not a feature request).
    4. When connecting via FTP, there is no chance to select connection parameters (e.g. to avoid insecure plain FTP and require FTPS).
    5. When importing from a non-HTTPS site (Wordpress), the validation of the import fails as it tries to open the HTTPS source site (which is non-existent, see log below).

    Thanks in advance for filing the change requests / bug reports, and improving the manual. Also, until PMT-4498 (https://support.plesk.com/hc/en-us/articles/360007391054) is fixed, you should visibly provide instructions within the tool how to clean up after a successful migration.

    info.log part for the last item:
    [2020-07-23 00:00:00][INFO] Check URL 'https://example.com/'
    [2020-07-23 00:00:01][ERROR] A web page returned by the source server has no HTML title.
    The web page URL: https://example.com/.
    [2020-07-23 00:00:02][INFO] FINISH: Check migrated applications

    0
    Comment actions Permalink
  • Avatar
    Bulat Tsydenov

    Hi b_p!

    Sorry for delayed response and thank you for detailed feedback.

    > At least in the German translation, when you open the Import tool, the heading shows a link to "switch to simple mode" even though the simple mode is selected. If you follow the link, the advanced mode will be shown, but the link text always remains the same.

    I reported it to responsible department, it will be fixed in future updates.

    > The wording source domain name is misleading. If transferring a domain "example.com", I would assume that I need to enter this domain name here. However, it turns out that you refer to the source (FTP/SSH) host name here. This is not clear at all and needs to be fixed. Especially with commercial hosting companies, the FTP server name is often completely different to the actual domain name.

    > In my case, I tried to import a website from a server where the (virtual) root directory for the FTP server does not coincide with the actual server root directory (and where the HTTP docroot is a subdirectory of that virtual root (e.g. /example.com where the actual path name in the server file system would be /var/www/clients/clientXY/example.com). I interpreted the instructions of the import tool such that in this case, I would need to set the "source document root" to "/example.com". Instead, I actually had to provide this as "files root". This is completely misleading. So please improve the descriptions (and do so without asking me to file a request on uservoice.com! This is a clear usability BUG and not a feature request).

    I will bring these both items to developers' attention.

    > When connecting via FTP, there is no chance to select connection parameters (e.g. to avoid insecure plain FTP and require FTPS).

    We have an internal request to implement it in future releases, however, I cannot say for sure when exactly it will be released.

    > When importing from a non-HTTPS site (Wordpress), the validation of the import fails as it tries to open the HTTPS source site (which is non-existent, see log below).

    I've just tried to reproduce it, I installed Wordpress and disabled HTTPS for the domain. As a result, Site Import extension showed me this:

    So, I continued and it worked fine. It would be great if you share exact steps to reproduce the issue if it is still reproduced.

     

    0
    Comment actions Permalink
  • Avatar
    b_p

    Bulat Tsydenov Thanks for the update. Unfortunately, I do not have any non-SSL site to import right now and not the time to reproduce it. Let's hope the bug is fixed now...

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request