To DO management responsible for product strategy:
Regarding the issue of adding additional IP addresses to a single Droplet... There is more to this issue than meets the eye.
I fully understand the business logic of limiting IP address space in order to sell more Droplets. You make it hard for an administrator to do too much with a single Droplet, so that s/he will have to have multiple Droplets to answer their business need.
However, this is short-sighted, both economically and strategically. The theory may work in an isolated system, but we don't have that in this case, we have a free-market system with lots of providers to choose from. The sysadmin will be more concerned about time lost managing multiple (unnecessary) Droplets, when one larger one could just as easily do the job if it could support multiple IP addresses. So the time-focused sysadmin would choose a different provider, and DO will lose out there.
The sysadmin's manager will have issues with his/her time being eaten up managing multiple Droplets, but they will also be focused on the price. Yes, DO is reasonably priced, but this manager will be forever asking "why do we need 17 of these for such small web apps? Wouldn't one Droplet with 17 sites do the job?" And the answer is, yes it would of course, if Droplets could support multiple IP address. So you may get some business from this kind of user, but after a bit of growth (and a budget review or two) they would eventually move elsewhere too, and DO would lose out again.
Then there's the independent freelancer, who makes websites. There is almost always an accumulation of such sites for smaller clients who cannot (or don't want to) provide staff and skills to manager their own hosting infrastructure, so they frequently ask the developer to do it. Cloud virtual server products are perfect for these developers, because they can just tack on new clients as they come up and increase their virtual infrastructure from time to time. They want to spend their time developing, and don't have time for managing multiple servers. They will prefer to use management platforms like cPanel or ISPConfig in order to provision and manage sites with a minimum of technical activity. These are the people you appear to be targeting in your demographic, but without supporting multiple IPs you aren't really targeting that market effectively. You are only appealing to the segment with enough staff and paying clients to maintain a Droplet for each client. But the fact is that there are MANY MORE one-person operations than multi-staff freelancers. If you want to own that market segment, look at what they need and give it to them. They want multiple IP addresses? So give it to them. So what if there are complex alternative ways to solve the problem... they haven't come here for that. They've come here to see if they can move all their clients into a Droplet with a minimum of technical fuss. Reverse proxies and new protocols with partial browser support may be one answer, but it's not the one they are looking for.
You'll notice also that the people active in this thread (and in similar discussions on AWS fora) are not just very keen on getting multiple IPs - it is actually a deal-breaker for them. And looking at some of the comments above, they are not just accepting the situation - they are in fact BITTERLY DISAPPOINTED that they can't use DO because of this.
But let me give you the biggest reason why you need it. Amazon doesn't do it. Yes, they offer multiple IPs on their VPC systems, but on standard EC2 EBS-backed instances, it is not available. And yet there are new posts every day asking for it. If DO was my business, I would be championing a serious case to push this feature through without delay. When it is ready, it just needs a few well-placed posts in some of those AWS threads discussing this issue, and people will jump ship in droves.
If it was me, I would be pushing this through as quickly as possible. There is a groundswell of need for this (as you see) and so it is only a matter of time before Amazon offers it on EC2. They may even be working on it as we speak. So get this feature done, roll it out and announce it everywhere, before Amazon does it.
P.S. The same applies for adding extra storage to a single Droplet. Although that isn't as urgent as the IP issue, because the rest of the providers in the market already offer it.
Geoff.
I'd love to be able to just get additional private IP addresses. Services like pacemaker and pgpool require a virtual IP address, and in our scenario, private IP addresses would work.
I'd be willing to pay the $5 cost of another droplet to be able to associate a second IP address with an existing droplet.......
Is there anything happening around this?
ns2.n server .. but I want to and take me to another website ip address.
How to Migrate DigitalOcean Snapshots Between Regions
Hope this helps