Changing the IP of a lightsail instance after installing it

[paulwellnerbou]

I would like to update my wireguard VPN server (using Lightsail), so I follow the recommendation and setting up a new server (although this means that I will have to send out the new configurations to all users).

I need to attach a static IP to the VPN server. But as ansible is creating the lightsail instance, I can't add the static IP to it before installing.

How can I do this, what would be the recommended way?

• Create the server before and use local provider afterwards to install it? Where do I provide the ssh keys then?
• Let algo set up the server and change the IP afterwards? (I tried this, and replaced the IP in all configuration files afterwards, but I get a ERROR:There is already a certificate for /CN=<IP> when updating users then)

Thank you!

[davidemyers]

Unfortunately the Lightsail API does not provide Ansible the ability to assign a static IP address during instance creation.

Using the local provider is what I imagine most people do, just remember to open the necessary ports in the firewall. When creating the instance look for the option Change SSH key pair and use your own key.

It should be relatively easy to change the IP address after the fact with WireGuard, but I think it's impossible to do that with IPsec, which sounds like what you've encountered. If you don't need IPsec you can try to deploy with ipsec_enabled: false in config.cfg and maybe ./algo update-users would work.

Another approach to to modify the Lightsail code to insert a delay to give you time to manually assign a static address, as discussed here. I've not tried that.

[paulwellnerbou]

Thanks, the waiting seems to work perfectly. I was afraid that this wasn't possible as the installation routine might keep the original IP somewhere.

Trying again now... I had problems with DNS resolution with dns encryption enabled. Will switch it off now again and retry.

[ahmed2m]

Does this look good? I really can't get it to work if I made the lightsail instance.
My logs looks exactly like the one posted in #1569

[davidemyers]

This is what Algo creates when you do a cloud deploy, so it looks like you've gotten it correct:

[ahmed2m]

For some reason even after rebooting it just doesn't let me through, I will try the time.sleep workaround for now.

[davidemyers]

I just did a "sleep" deploy and it appears to work fine with WireGuard.

It's great to see that Lightsail finally has IPv6. I may switch over from EC2.