The issue with Bubble.io regarding a static IP is that Bubble.io, especially on its lower-tier plans, does not offer dedicated IP addresses for applications. This can pose a problem for certain integrations or services that require requests to come from a specific static IP address.
For example, integrating with my local SMS service, which requires a static IP for security reasons, becomes challenging because Bubble.io cannot guarantee that the outgoing requests will originate from the same IP address every time. This limitation can hinder the ability to establish secure connections with services that rely on whitelisting specific IP addresses for access.
Are there any workarounds or successful recommendations for this issue?
Have you thought about proxying the requests through some 3rd party server space. Perhaps something like a basic droplet at Digital Ocean ($6/month) and passing the request through there?
Thank you for your recommendation. We have tried to find and test many workarounds. However, I was hoping that Bubble would allow it as a new paid feature for the lower plan, as Bubble already provides it in the dedicated plan.
You could proxy it through AWS elastic IP as well.
I guess tools like Zapier, Pabbly has static IP option for specific integrations. In case if you want to route just that API outside bubble.
It is actually quite unfortunate that bubble only provides this in dedicated plan
