Move to larger AWS instance

QRM

• March 23, 2016 08:12

I created a t2.micro instance on AWS E2. Everything has been running swell. I decided to hire ConfigServer to setup my firewall. Their support team indicated some of the firewall services were clobbering the 1GB Ram limit on my t2.micro instance. I created an AMI on a 8GB Ram instance and reallocated the elastic IP to the new device. Unfortunately, I got a license error page even though the elastic public IP is the licensed IP. I can SSH to the larger EC2 instance on the licensed IP. I thought there may be an issue with the new private IP allocation of the AMI. AWS does not allow you change the private IPs on an instance. The t2.micro is 10.0.0.242 and the M4.large is 10.0.0.79. /usr/local/cpanel/cpkeyclt failed on the new instance. What do I need to do to properly migrate my machine image and get it running the way it should? Thank you. Tom

• 

  cPanelMichael

  • March 23, 2016 16:10

  Hello :) Could you verify if you are using the AMI offered by cPanel? There's a post on it at: Unable to install on Amazon Linux It's unrelated to your specific issue, but it explains how to use the supported cPanel AMI (no others are supported). Thank you.

  0
• 

  QRM

  • March 23, 2016 19:19

  Michael, I performed a direct install on my t2.micro EC2 CentOS 7 (x86_64) with Updates HVM instance. I felt I had a good server running. So do I need to rebuild an m4.large instance from scratch via the cPanel AMI? Is there anyway to migrate kernel update, extensions, ConfigServer plugin, PHP, MySQL upgrades, Pure-FTP passive port range, etc? Thank you.

  0
• 

  cPanelMichael

  • March 23, 2016 23:10

  You should not have to migrate your data, however going forward it's a good idea to ensure the cPanel AMI is utilized. As far as the license issue, could you let us know the specific error message you receive when attempting to update your license? Are there any entries in /usr/local/cpanel/logs/license_log that offer more information? Is the correct IP address listed when running the "curl -L

  0
• 

  QRM

  • March 24, 2016 03:55

  Michael, Thanks. I've been waiting for my B2B ecommerce site to calm down. I deleted my m4.large instance this morning. I'm going to launch a new one, associate the elastic IP and run the show IP command from SSH. I'll report back shortly.

  0
• 

  QRM

  • March 24, 2016 04:45

  Correct IP (Elastic) on the m4.large EC2 instance: root@ip-10-0-0-165 [~]# curl -L

  0
• 

  cPanelMichael

  • March 24, 2016 17:26

  I'm going to launch a new one, associate the elastic IP and run the show IP command from SSH. I'll report back shortly.

  
  If you are proceeding to launch a new instance, then it's a good idea to go ahead and use the cPanel AMI. Could you let us know if the issue persists when doing so? Otherwise, check to ensure 1:1 NAT is enabled: 1:1 NAT - Documentation - cPanel Documentation Thank you.

  0

Please sign in to leave a comment.