I’ve added the custom domain to my site, however, I wouldn’t expect it to be ‘Connected’ because that domain name is pointed towards my nginx server, not to webflow’s proxy server.
With the nginx config you posted, nginx will proxy the request to our server without changing the hostname of the request. Since we do dynamic routing based on hostnames, the hostname included in the request must actually match the site you are trying to proxy to.
I think the additional line in the location block of your config you need is this:
In the end, I ended up setting up the webflow site on a different subdomain (wf.canimmunize.ca), which allowed the domain to be properly connected to that subdomain. And then I proxied my desired domain to that subdomain like so:
we have been struggling around for quite a long time to find the correct settings.
In the end it was easier then expected.
Feedback from the official support was limited helpful, that’s why I want so sum up the steps I did.
Here’s the official response I got from Webflow support regarding partial site hosting via reverse proxy. Note that Webflow now allows for href prefixing in the custom code advanced options.
The way to setup the connection in Webflow is to create a subdomain using a cname record to point to proxy-ssl.webflow.com.
For example, if you create a subdomain of the root domain called “connect” then point “connect.yourdomain.com” at proxy-ssl.webflow.com and add that domain to the hosting tab of project settings in Webflow.
Next, in your reverse proxy, the url that you will use to pull the pages from Webflow will be: https://connect.yourdomain.com.