Cloudflare configuration for Sendgrid setup SSL for Click Tracking

Need help
1

Hi all,

We are trying to setup SSL links for click tracking using SendGrid app, which the needed steps are explained here.

And in its documentation they explain how to configure Cloudflare.

See SSL Full setting.

So my question is: is there a way we can access to Cloudflare account of our Bubble app and configure it for this purpose?

Thanks in advance,
Opground team

2

Hi @mgozalbo,

You’ll need to configure it in your domain’s DNS settings. Your Bubble app is protected under Bubble’s Cloudflare account, but your app’s domain and DNS settings are managed by you.

1 Like
3

Thanks for your support @johnny!

The thing is I’ve already configured successfully my domain’s DNS settings in order to have a CNAME entry for pointing all the SendGrid branding links like “url3333.mydomain.com” to “sendgrid.net” that is required for having a better reputation pointing to our server instead of directly to “sendgrid.net”. But the issue is the side “url3333.mydomain.com” is responding with a “sendgrid.net” certificate, giving ERR_CERT_COMMON_NAME_INVALID error, since the domain name is not the same as SendGrid certificate. I found some thread related: email - SendGrid Link Branding gives ssl issue - Stack Overflow

So I was wondering how I can do the “TLS passthrough” with Cloudflare, but since I have no access to its configuration, maybe I’ll have to do it manually with a proxy explained here… :frowning:

4

Hm, are you using Cloudflare yourself as your DNS provider?

5

Hi again @johnny, I am using a hosting provider that internally uses a CDN (not sure which one) that I have no access to configure it since they are providing all the management.

But at the end I went with setting up a proxy with AWS API Gateway and now I have SendGrid SSL open&click tracking feature up and running properly :rocket:

6

Furthermore, I’ve created a quick guide in order to explain the steps I did in AWS API Gateway inspired on the SendGrid guide:

  1. Create a new REST API with a proxy resource for forwarding traffic to https://sendgrid.net/{proxy}

  2. Create a valid SSL certificate for your link branded domain with AWS Certificate Manager and create a custom domain name.
    → Map the new custom domain name to API: HTTP API mapping.

  3. Forward the Host HTTP header with your link branded domain.
    → Capture Host header parameter in HTTP Request Headers section of Method Request configuration in ANY Method Execution window.
    → Map Host parameter in HTTPS Headers section of Integration Request configuration in ANY Method Execution window with method.request.header.Host expression.

  4. Point the CNAME record at your hosting provider to your proxy. For example, CNAME mailing.example.com proxy.example.com, where proxy.example.com is the API gateway domain name of the custom domain.

  5. Publish API

Hope it helps!

7

This topic was automatically closed after 70 days. New replies are no longer allowed.