Skip to main content

Issues after the server migration - WHM to WHM

Comments

14 comments

  • ffeingol

    Not quite enough information.  Did your name server IP's change?  If your name servers IP's did change did you change them both in the DNS zone and at your domain registrar?

    0
  • HeyHost

    Well, I did create new nameservers for the new server and that works. 
    These are ns1.maindomain.com and ns2.maindomain.com
    The previously working nameservers on the old server are ns3.maindomain.com and ns4.maindomain.com.
    I used WHM transfer tool and first migrated all accounts from old server to the new one. And that worked fine.
    When I migrated the maindomain.com to the new server the old server stopped working and I could not get it running. Because the transfer tool suspended the account at the old server I could not get into the domain. So I did find the way to unsuspend the maindomain.com at the old server and changed the nameservers back to the previous ones ns3. and ns4. 
    Now hours later the maindomain.com is still down. 

    0
  • cPRex Jurassic Moderator

    It sounds like Live Transfer happened so everything is pointed at the new server, which is why updating the DNS wouldn't matter since we setup proxies to the new machine once the transfer is complete.

    Does this sound like your situation?  https://docs.cpanel.net/whm/transfers/transfer-tool/#live-transfer

    0
  • HeyHost

    Yes, this is what is happening.
    I am following the instructions from :
    https://docs.cpanel.net/whm/transfers/transfer-tool/#live-transfer
    And it says I should change the Hostname to stop the new server from pointing to the old one. 
    Is that correct?
    Will that break things on the old server?

    0
  • cPRex Jurassic Moderator

    If you need to under the Live Transfer settings and point things back to the old machine, we have an article on that procedure here: https://support.cpanel.net/hc/en-us/articles/360051936854-How-do-I-revert-the-changes-made-by-the-live-transfer-feature-in-the-transfer-tool

    0
  • HeyHost

    Thank you!
    I just wish you have answered this on Friday, it would save me my hair...
    I am going through the steps and I try these commands but I get error:

    whmapi1 unset_all_service_proxy_backends username=$username

    username=$username  - Do I change the first username with a real username or both as if changing the $username to $realusername says: API Failure the value "username" cannot be empty ?

    0
  • cPRex Jurassic Moderator

    The variables you want to change are always the ones with the dollar sign.

    0
  • HeyHost

    I tried all three combinations of that command and I still got an error

    [root@zaf ~]# whmapi1 unset_all_service_proxy_backends username=$saredxzsw
    ---
    metadata:
      command: unset_all_service_proxy_backends
      reason: "API failure: (XID wcab8g) The value of “username” may not be empty."
      result: 0
      version: 1
    [root@zaf ~]# whmapi1 unset_all_service_proxy_backends saredxzsw=$username
    ---
    metadata:
      command: unset_all_service_proxy_backends
      reason: "API failure: (XID rzds23) Provide the “username” parameter for the “Whostmgr::API::1::Accounts::unset_all_service_proxy_backends” function."
      result: 0
      version: 1
    [root@zaf ~]# whmapi1 unset_all_service_proxy_backends saredxzsw=$saredxzsw
    ---
    metadata:
      command: unset_all_service_proxy_backends
      reason: "API failure: (XID htkzm6) Provide the “username” parameter for the “Whostmgr::API::1::Accounts::unset_all_service_proxy_backends” function."
      result: 0
      version: 1

    0
  • HeyHost

    Ok so its not working for some reason.
    Or, should I omit the dollar sign?

     

    0
  • cPRex Jurassic Moderator

    You have to remove the dollar sign before the username - sorry if that bit was confusing.  In general in programming, $word indicates a variable, and that the dollar sign is also removed when you modify it.

    1
  • HeyHost

    Thanks, no problem. I am learning. 🙏👌💪
    I have run 2 , 3 and 4 commands and now for 5:

    For $oldIP do I put that old (source) server where I want the domain to end up again? Or will my old one now be the new server's IP?

    cut -f1 -d":" /etc/trueuserdomains | while read x; do /usr/local/cpanel/bin/swapip $oldIP $newIP $ftpIP $x; done
    0
  • cPRex Jurassic Moderator

    Correct - oldIP is the IP of the Source machine.

    1
  • HeyHost

    Thank you! 🙏

    0
  • cPRex Jurassic Moderator

    Sure thing!

    1

Please sign in to leave a comment.