Skip to main content

Full restore (cpmove) doesn't restore subdomains

Comments

5 comments

  • PeteS
    Hmmm... Maybe I spoke too soon. The file structure appears to be correct, compared to the old server. (My initial analysis seems to have been premature "I checked the file structure and the subdomain subdirectories exist and are empty except for an empty CGI folder. Surely that's not the problem, that it creates the subdomain folder and the default CGI subfolder, and thus it is not empty, so fail?" This actually is correct, right?) So why the warning?
    0
  • PeteS
    So why the warning?

    I have my answer... after DNS switched I'm getting 403 on subdomain.example.com and example.com/subdomain. Can anyone tell me what's going on here?
    0
  • cPanelMichael
    Hello Pete, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.
    0
  • PeteS
    Hello Pete, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.

    Actually I just sorted it out... The old server (no root access, so I have to guess on some of this) is set up as: /home/user/subdomain (contains the content) with a symlink from /home/user/public_html/subdomain (with no content, but pointing to the content) and subdomain.example.com pointed to /home/user/public_html/subdomain. It wasn't this way in the past and I don't know when they changed things, but it's a bit odd (and part of the reason it's the "old" server - I'm leaving that sinking ship). The new server is the normal /home/user/public_html/subdomain only, with subdomain.example.com pointed to /home/user/public_html/subdomain. It looks like cpmove doesn't know what to do with that. All I had to do was move the content to the empty (thus 403) folder o the new server and all's well. If that all sounds right to you then we're done and you can mark it solved. Someone else may run into this same issue and hopefully this will help. -Pete
    0
  • cPanelMichael
    Hello Pete, I'm glad to see you were able to determine the cause of the issue. I'm marking this thread as solved. Thank you.
    0

Please sign in to leave a comment.