Support » Plugin: SiteGround Migrator » not properly working inside siteground

  • I have tried to transfer my template installation from one SG account to another and I couldn’t do it in any way.

    I also opened tickets and chats to the developers inside SG support system and they could not find a suitable solution.

    Very disappointed

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Hristo Pandjarov


    SiteGround Representative

    Please, open a ticket in your Help Desk and not a chat session with our customer care representative.

    The plugin transfers thousands of sites each day successfully including sites from one SG server to another. There’s something in your particular setup that prevents it from working properly – most probably a security plugin or restrictive rules in your .htaccess files.

    You can see the exact reason in the siteground-migrator.log file in your wp-content folder.

    However, a ticket in the technical assistance section should help you out.

    Hello and thank you for your reply, as well, Hristo.
    Are you saying that I have a misconfiguration, just because it works on your computer?
    And I should read all the logs to find the solution, while you can be so sure, without even know the websites I’m working on, that it must be a misconfiguration on my side?

    Of course, I opened tickets on both the source account and the destination account.

    I had the two teams been working for 4 days on the issue, without solving. But maybe you are so smart you can give your precious help to SG support gurus Dimitar and Levis, that cannot be able to find the misconfiguration and of course, they haven’t thought to read the logs…

    In any chance, if you want to be a better developer, next time you may try to understand the issues before answering and of course as a SG Representative, you may learn to open your replies with:

    Hello, thank you for using our plugin, I’m afraid to know you had this issue, how can I help?…

    Good luck with your career, anyway.

    Plugin Author Hristo Pandjarov


    SiteGround Representative

    Sorry if my reply felt rude or something – that wasn’t my intention. All I am saying that there’s no global issue moving from one SiteGround account to another because me and my team monitor the migrator stats constantly.

    I’ve found your account and checked your ticket history. My colleagues have explained that there’s permissions problem and you need to open another ticket from your other account. That’s simply because we have strict authentication procedures and can’t just interact with our customers data without their permission. Then one of my colleagues has done a mistake with one of their reply. I will make sure he receives the appropriate feedback.

    Next, I’ve checked your case and the log confirmed my suspisions – rules in the .htaccess file in your from location have blocked the transfer from completing:

    RedirectMatch 403 (?i)\.(aspx?|bash|bak?|cfg|cgi|dll|exe|git|hg|ini|jsp|log|mdb|out|sql|svn|swp|tar|rar|rdf)$

    Our plugin encrypts and archives your content before migration and then moves the content. With the rule above active, all requests to .tar files return 403 forbidden error causing the transfer to fail.

    I can see the site is transferred now and both installations look the same. If you continue having issues, let me know, I will do my best to help 🙂

    Hi Hristo.
    Thank you for your apologies, they are more than welcome.
    Unfortunately, you only read half of the story, for I have opened the issue on the other account and on April the 9th your colleague Borislav replied the following:

    I carefully reviewed your case, and I fixed permissions of the following folder to files 644 and folders 755:


    Please, start the website transfer again.

    If the issue persists, please update this ticket.

    Best Regards,

    Borislav XXXXXX
    Technical Support Team

    I tried to transfer back, but I encountered the same issue.

    So this morning I proceeded in the old way manually transferring the plugins and themes directory.

    This is the reason for my low rating.
    I’ve been using your plugin several times with no issues, even for big installations, but never from SG to SG.
    Having the chance to transfer between these two accounts is very important to me, for will need often to setup my new templates WP installations from my main account to the resellers’ ones.

    So please, try to investigate deeply this issue because the solution you proposed didn’t work. Working as a roadwarrior developer, I don’t always have the chance to rely on fast connections and your plugin would save my time and my bandwidth.

    Take care

    Plugin Author Hristo Pandjarov


    SiteGround Representative

    I am 100% sure it’s the security rule in your .htaccess blocking it. When you migrate sites, just use a standard WP .htacces and then apply the rules on the new account once the site is transferred. In addition, disabling all security plugins is a good idea too in general but here the error is pretty straight forward.

    Hi Hristo,
    I had a look at the .htaccess and I think your answer is correct.

    Now I wonder where those directives come from since the only “security” plugin is the SG Optimizer. I will delete it in my template for the next migrations and I will clean the .htaccess up as well.

    I will let you know if I’m facing the same issue again: I’m not trying now, for I’ve really wasted a lot of time on this installation.
    Take care

    Plugin Author Hristo Pandjarov


    SiteGround Representative

    Hey Mirko,

    I mentioned security plugins as a general suggestion. In your case it’s just the rules in .htaccess file 🙂 Maybe at some point you’ve added them manually, or tested out a plugin that didin’t clear after itself upon deactivation. The SG Optimizer does not add security rules to the .htaccess file.

    Give it a try, I am sure it will work just fine.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘not properly working inside siteground’ is closed to new replies.