What about to use floating IP. I means: if i create a floated IP , i think that it doesn’t change or disappear while i monthly pay $4. So, i could have a “destroyed” droplet (previously i would take an snapshot) and then i could deploy again a new droplet with that snapshot and assign it to the same floating IP.

Obviously, the subdomain/domain has always been configured in its DNS record A to point to the floating IP.

My question is this: the SSL Let’s encrypt certificate can be configured in this architecture without any problem?

I’ve seen that:

• when you create a droplet, it gets an IP
• when you assign a droplet to a floating IP, you can reach the droplet (for example using SSH) through both IPs
• if from the droplet i make a WGET call to a server, its public IP is NOT THE FLOATING IP, but the first IP (!!)

So, if once assigned the droplet to the floating IP i install the Lets Encrypt certificate, which IP will be taken? The ideal thing would be the floating IP, in this way we can destroy the droplet and deploy it again from an snapshot as many times we need more “load capacity” in the future, and the SSL certificate would run fine as the first day.

But i suspect that it’s not easy. Please, can someone put some of light on how get this solved?

If i could request to DigitalOcean, i would ask for be able to pay for maintain my droplet IP although i destroy the droplet, paying that monthly $4 (as for a floating IP). Is it possible?

Many thanks in advance for any help. I’m new to this wonderful world of cloud hosting services! ;-)