Consent Pro works perfectly on Webflow staging and on Netlify using the exact same export. It fails only on our production server. The preferences modal opens automatically and cannot be closed. The form displays the Webflow error message. Could you help us identify whether there are known server requirements or compatibility issues with exported sites?
Hey @fwilzius! The fact that the identical export works on Netlify but fails only on your production server is actually a useful clue — it points to two specific things worth checking in parallel.
License domain configuration
Consent Pro requires an active license tied to your specific custom domain to work on self-hosted sites. If your production domain isn’t registered in your license, the script won’t initialize — which lines up with the preferences modal opening automatically and being uncloseable.
Check that the exact domain your production server is serving on is listed in your Consent Pro license configuration. If Netlify is deploying to a preview URL like yourproject.netlify.app rather than your actual custom domain, that would explain why it works there but not in production. You can manage your license domains at my.finsweet.com/plans.
Content Security Policy headers
This is a known issue for server-hosted Consent Pro deployments. If your production server sends a Content-Security-Policy header with a restrictive connect-src directive, the browser will block Consent Pro from reaching its verification servers.
Open DevTools on the production URL and check:
- Network tab — look for failed requests to
api.consentpro.com - Console tab — look for CSP violations like
Refused to connect to 'https://api.consentpro.com/v2/license/verify'
If CSP is the issue, add this to your connect-src directive:
connect-src 'self' api.consentpro.com *.consentpro.com [your other existing domains...]
On the form error — that’s actually a separate issue. Webflow’s native form submission only works when hosted on Webflow. On exported sites, there’s no backend endpoint, so you’ll need a third-party form handler like Formspree or Basin.
To help narrow things down, could you share the exact production domain, any console errors or network failures from DevTools, and whether your server has any security headers configured? 
Here is the link to the docs