Source IP / subnets / CIDR for baserow.io webhooks?

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

Some web services which emit outgoing webhooks sometimes provide the authoritative list of source IPs for the machines emitting the webhooks (for example stripe does this). Does baserow publish such a list of webhooks coming out of baserow.io ?

Hi @lucw, we don’t currently publish such a list, but it is indeed not a bad idea. Maybe we could do that @bram?

So far it looks like webhooks come from two distinct IPv4 addresses.
By the way, as a product on the leading edge of modernity and open standards, I encourage you to support IPv6 on baserow.io one day. My self hosted instance is fully IPv6 enabled.

That is an interesting question @lucw. At the moment we don’t have fixed IP addresses for the outgoing webhooks. baserow.io is hosted on a Kubernetes cluster that automatically drops and spins up nodes based on the demand. Each of these nodes has their own IP address, but can be destroyed. I’ll discuss with the devops team whether we can introduce fixed IP addresses for the celery workers responsible for calling webhooks. Once we have that, we can communicate those IP addresses.

Hey @lucw, I checked with the team, but apparently we already have this. There are two IPs attached to the NAT gateway that sits in front of all our nodes. It will either be one of these IPs. We’ll add it to the documentation.

3.77.114.147
35.158.33.248

Those are the two IPv4 addresses I found in my empirical testing as well. Thank you so much.