Switching to a resized lightsail instance
I'm currently running WHM & Cpanel on the smallest lightsail instance that is attached to a static ip. Today I took a snapshot of the instance and started a bigger lightsail instance from it. I reattached the ip to the new bigger instance, but my website does not work when attached to the new instance and shows me the standard cpanel error page saying the server might have changed and asking to contact the admin.
One of the reason I used lightsail was because I believed I could instantly switch to a bigger instance when I hit traffic. Why is this hard to do? What am I missing?
Thank you..
-
Hey there! Did the IP address change when you made the switch? If so, you'd need to wait for DNS propagation to complete in order for things to work well, but the most common reason people get the "Sorry" page is because the domain is routed to one IP address but Apache is listening for the site on another. 0 -
Since I'm using a static ip, the ip change was instant to the newer more powerful instance. But I hit the sorry page. I remapped the ip to the original instance and my site began instantly working again. Last week my site hit a lot of traffic that bought my server to its knees. I was tempted to start a new instance from the snapshot (for which purpose I got a static ip in the first place). But I developed cold feet because I hadn't tested it before. And the test I did the following day failed. Is there anything I can do to make the shift to the new instance, instant? Without which my setup does not feel very scalable and does not give me the benefit of being on lightsail. 0 -
if the remap process had to be done on the Amazon side of things, there isn't more you can do in cPanel to make it faster as that would be up to them and how they perform the resize. 0 -
I expected I did something wrong, but if the issue is with cpanel than what hyperscale are we talking about here? I cancelled my subscription after this. Might as well pay that $15 to increase my instance size because I'm just running a single website. 0 -
It's important to note that we don't officially support changing the NAT IP address after a server is created. We have this outlined in our documentation here: "We strongly recommend that you only perform these actions on a new installation of cPanel & WHM. Do not attempt a 1:1 NAT configuration on an existing production server." 0 -
@Sid88, did you ever find a resolution here? Having same issue with creating new instances from a snapshot on lightsail. Even when a fresh cpanel instance is created, cpanel has finished installing and a manual snapshot is taken. That new instance from the snapshot is completely unresponsive to both SSH and browser access through port 2087. 0 -
This issue has been resolved for myself. An OS update to the package cloud-init solved the networking issue. The issue was system_info['variant'> value was not matching up to KNOWN_DISTROS in cloud-init. Hurray! 0 -
The solution for me was to use WHM's 'IP Migration Wizard' and change the old instance's private IP to the new instance's private IP.
0
Please sign in to leave a comment.
Comments
9 comments