My advice: First upgrade to 3.3 and then build the second node. With that, you don't have to deal with this problem. I don't remember with which version it changed, but newer releases give you the option to trust the certificate when you add the new node to the deployment.
For your actual setup, there are likely two ways to go (at least what the error message suggests):
1) Import the Admin certificate from the second node in the trusted store of the first node.
2) Configure the second node with a certificate from your PKI, (the same PKI that issued the certificate for the first node).
After one of these, the deployment should build. And if you only changed the IP, you also have to change the hostname and add it correctly to DNS.