We’re reaching out regarding an issue we’re facing while trying to integrate one of our Webflow-hosted pages within a partner institution’s domain using a reverse proxy setup.
Context:
Our main website is hosted on Webflow at: https: futurense dot com
The IIT Mandi Centre for Continuing Education (CCE) team is attempting to make this page accessible from their institutional domain (e.g., https: cce dot iitmandi dot ac dot in/…) through a reverse proxy configuration.
However, upon setting up the reverse proxy config from the partners end, their server is encountering the following error:
Proxy Error: The proxy server could not handle the request.
Reason: Error during SSL Handshake with remote server
What We Have Tried
Updated the ProxyPass and ProxyPassReverse directives to use HTTPS instead of HTTP.
Verified that the Host header and client forwarding headers are configured correctly.
Confirmed that outbound HTTPS traffic from their side is working.
We also have the following security settings enabled on our Webflow project:
a. Enable HSTS for subdomains
b. Enable HSTS preload header
c. Use secure frame headers
Can anyone please let me know how can I fix the reverse proxy issue that I am currently facing? To give more information, we are using Cloudflare as our DNS provider for futurense dot com**
Webflow does not support reverse proxies for non-Enterprise customers. While you can use them, we cannot troubleshoot or guarantee connectivity in these scenarios.
For sites that need to work alongside an existing setup, we recommend using the Href prefix setting in your Site settings. This setting allows you to create a “sub-site” by adding a prefix to all internal page links.
If you’re specifically working with Cloudflare and experiencing SSL handshake issues, try temporarily disabling the Cloudflare proxy. You can do this by clicking the orange cloud icon next to your DNS records to switch them to DNS Only mode. This is especially important if your site hasn’t been migrated to Webflow’s Cloudflare infrastructure yet.
Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.
Hello, when you say Webflow does not support reverse proxies for non-enterprise customers, do you mean that there is no customer support for this or the technical setup itself is not possible for Webflow websites on standard plans? We are okay to upgrade to enterprise plan if this allows us to achieve the technical requirements
Hello @FuturenseDeveloper, reverse proxies are possible in non enterprise plans, however Webflow can not offer support for reverse proxy setups outside of enterprise plans. I hope this helps.
I do a lot of RP builds, almost exclusively using Cloudflare workers.
What is your RP built on?
It’s impossible to guess what configuration problem you’re facing without knowing your stack and digging into your configuration and code, But what is it you’re trying to build?
Do you mean that https://cce.iitmandi.ac.in is intended to be a full clone of your Webflow-hosted https://www.futurense.com site under a different origin?
You haven’t explained what you’ve built, or why you’re doing it this way rather than just simply making cce.iitmandi.ac.in the primary domain for your site.
But if you really need an RP it’s a straightforward site-mirror pattern.
You need to build a reverse proxy that-
Rewrites the Webflow-hosted HTML pages to your cce subdomain
Changing the canonical as well
Rewrites the Webflow-hosted sitemap.xml
Changing the <loc> origins and paths to match
On Cloudflare I’d use the new O2O configuration ( google it ) so that you don’t have to do any workarounds for Webflow’s SSL.