CDN Migration Reverse Proxy Help

Publishing help Project settings
1

Having a headache migrating a CloudFront Reverse Proxy & Route 53 setup to the new DNS.

Despite my best efforts to follow the requests on the Dashboard > Publish page we still have concerning warnings showing up.

My main question is: for a Reverse Proxy setup, are these warnings false alarms or real? I am concerned about publishing our site as I do not want it to do down.

I am hopeful that someone with a similar setup has already done this and can chime in.

I see the following warnings on Dashboard > Publishing

  • Production > Root Domain Update Needed SSL Certificate Update Needed
  • Production > www. Domain Update Needed SSL Certificate Update Needed
  • Publish Button > Production > www. Domain SSL Certificate Missing

See the following photo of the warnings in yellow:

Screenshot 2026-02-09 at 4.46.04 PM
Screenshot 2026-02-09 at 4.46.04 PM1920×1267 255 KB

The suggestion for the Root & www. Domains to fix the Update Needed warning is to update the CNAME record to cdn.webflow.com and the Root Domain A record to 198.202.211.1.

I have followed the instructions for the manual migration as it appears to apply for our configuration.

Note: for Route 53, we have the following configuration:

  • Root Domain, A record, Alias, <unique_id>.cloudfront.net.
  • www. Domain, A record, Alias, <unique_id>.cloudfront.net.

Note: Instead of a CNAME, under the CloudFront distribution, we have the following configuration:

I saw no reference to 75.2.70.75 or 99.83.190.102 and so am unable to add a reference to 198.202.211.1

The SSL Cert warning confuses me as we are using a still valid AWS issued SSL Cert attached to our CloudFront Distribution.

Other things I have tried (and since reverted):

I saw this Post (from an AI bot?) That says for a reverse proxy these warning messages are false alarms. However it also mentions the old variables in its solution 75.2.70.75, 99.83.190.102 & proxy-ssl.webflow.com

The suggestion seemed very very similar to the steps to setup a new custom domain.

So I tried following the steps from the setup a custom domain guide, by removing the CloudFront A records and replacing them with the desired A & CNAME records.

  • Root Domain (as well as @.), A record, 198.202.211.1
  • www. Domain, CNAME record, cdn.webflow.com

This changed the update needed warning under the www. Domain to connected permanently (while the CNAME was up) and the updated needed warning under the root domain to connected for a moment then back to updated needed.

I did notice that we do not have the TXT document referenced in the steps to setup a new custom domain.

It seems that this is a one time code (one-time-verification=) shown on creation for verification only.

I did not try removing our domains and creating new ones (seemingly the only way to get that code to appear). I was cautious about doing this as it could take the site down with no way to get it back up. If this is a solution please let me know.

I reverted these settings as they took the site down due to a lack of SSL certificate. Note the warnings where on our webflow publish page before I played with the A records in this way.

If you are still here - thank you for your time and attention.

Please share your thoughts. If I find a solution I’ll submit an update to this post.

2

Hi Holland, best to run this by support if you can.

I use Cloudflare exclusively for my RP builds so the configuration is a bit different.

In general, if you modify the DNS configuration from Webflow’s standard convention, it will give you warnings because it does not recognize the configuration. That also applies to the Cloudflare Orange-to-Orange ( O2O ) configuration- with is fully valid but still difficult for the dashboard to validate.