Hello everyone,
I seem to be facing a recurring issue with the integration between Webflow and IONOS. After reviewing all related discussions, I couldn’t find a solution that fully addresses the unique aspects of my case. The closest match was a thread where the user resolved their problem but didn’t provide a detailed explanation of how.
Here’s my situation:
The staging link of my site functions as expected, and any changes made in the Webflow editor are successfully reflected upon publishing:
However, the custom domain version of my site remains stuck in its June 2024 state, despite clearing the cache on five different browsers and testing across three devices. This rules out a cache-related issue.
Example: https://www.groupe-eco-solidaire.com/
Screenshot: (Capture of the issue not included here for brevity)
After investigating, I suspect the problem is related to the DNS settings between Webflow and IONOS.
- Webflow Configuration:
When using the “quick connect” feature to link my custom domain (groupe-eco-solidaire.com), Webflow fails to detect thewww.version of the domain.Screenshot: (Detection issue on Webflow not included here) - IONOS DNS Settings:
Below is a capture of my current DNS records on IONOS:
Screenshot: (IONOS DNS records not included here)
Based on forum discussions, I wonder if the issue could stem from the CNAME value. I noticed that when trying to manually add a trailing “.” to the CNAME value (as suggested in some guides), it isn’t applied.
Screenshot: (Error when adding “.” to the CNAME value not included here)
I’ve already reached out to support and am awaiting their response. In the meantime:
- How can I get Webflow to recognize the
www.version of my site? - Are there any tools or methods to troubleshoot these integration problems?
- Could the redirection to
www.groupe-eco-solidaire.com—which is stuck on the June 2024 version—be the root cause? If so, what steps can resolve this?
the answer from webflow support is very interesting:
"Thank you for following up.
The issue here appears to be that the www subdomain is connect to a different site under a different Workspace, with it’s own site plan. When the www domain is set as the default, the root domain will redirect to the www subdomain.
As a next step, can you check if you have another Webflow account which the www subdomain might be connected to? This would be the quickest path to resolution, as you could log-in with this alternate account and remove the domain from the current site → connect the www subdomain to the current site. "
I can confirm that the site is not live elsewhere on another workspace with a paying plan. It has simply been published and then unpublished on a parent account, duplicated and the duplicate transferred. It’s the transferred site we’re trying to make live, but without success.
Can you help me? Do you have any ideas?
Thank you in advance for your insights and support!
