I am re-engineering my websites to use clusters of containers rather than fixed servers (Amazon ECS). Due to the LimeLM API IP restriction I am going to have to maintain a separate stand-alone server just for my license store (and pay for this server 24/7). Nothing else I use has a restriction like this, including my credit card processor (Stripe).
I remain a fan of LimeLM but I have to explore other options; the IP restrictions are interfering with my infrastructure plans.
I'm not trying to re-open this can of worms, I just want Wyatt to know it is putting pressure on me to seek alternatives.
We're rolling out the ability to use up to 3 IP addresses at once per API key. This is coming in the next 2 weeks.
We're never going back to allowing any/all IP addresses that want to use an API key because that's insecure design and leads to abuse, leaked data, and lax security practices (and we saw that in real-life, hence the change in the first place).
I have no way of managing my web servers' IP addresses. I will always have more than 3 servers and have no control over their IPs. I will have a separate server just for LimeLM tasks until I no longer need it.
Every major “web hosting service” (e.g. Amazon, Google, Microsoft, and the thousands of VPSes) offer the ability to use either static IP addresses or pools of IP addresses. Some provide them as part of the service. Others charge extra for them. It depends on the service.
Google for the details for your particular service.
I know how to use static IPs on AWS; my special server just for LimeLM uses one! The rest of my web traffic goes to ECS clusters of containers. There is no way to have a single IP for that traffic.
