Can a wildcard certificate from a client's own server be used in a Webflow project instead of using the SSL provided by Webflow?

Published on

September 22, 2023

Note

CommunityFAQ is not affiliated with Webflow. Click here if you'd like to visit Webflow's help resources.

A wildcard certificate from a client's own server can be used in a Webflow project instead of using the SSL provided by Webflow. Here's how:

Generate a wildcard certificate: The client needs to generate a wildcard certificate from their own server or a trusted third-party certificate authority (CA). This certificate should cover the domain and any subdomains that will be used in the Webflow project.
Export the certificate files: Once the certificate is generated, the client needs to export the certificate files, including the private key and any intermediate certificate files, in the appropriate format (e.g., PEM or PKCS#12).
Configure SSL settings in Webflow: In the Webflow project settings, go to the Hosting tab and click on "Enable SSL" under the SSL options. Choose the "Manual SSL" option.
Upload the certificate files: In the SSL settings, there will be fields to upload the certificate files. Upload the certificate file, private key file, and any intermediate certificate files in the designated fields.
Verify and activate SSL: After uploading the certificate files, Webflow will verify the certificates. Once verified, click on the "Activate SSL" button to activate SSL for the custom domain and subdomains.

It's important to note that using a wildcard certificate from a client's own server requires technical knowledge and access to server administration. If the client is not experienced in managing SSL certificates, it's recommended to seek assistance from a qualified professional to ensure the correct configuration and installation of the certificates.

Additionally, using a wildcard certificate may limit some features provided by the Webflow SSL, such as automatic renewal and easy management through the Webflow dashboard. Regular renewals and management of the wildcard certificate will be the responsibility of the client.

In summary, while it is possible to use a wildcard certificate from a client's own server in a Webflow project, it requires technical expertise and manual configuration. It's essential to handle the certificate files securely and stay up to date with certificate renewals to maintain SSL functionality.

Additional Questions:

What are the advantages of using SSL in a Webflow project?
Can I use multiple SSL certificates for different subdomains in Webflow?
How can I check if SSL is properly configured on my Webflow website?

Is it possible to achieve the user flow described, including the integration of Webflow user accounts with Razorpay for subscription payments?

What is Webflow's role in colo.life?

What is the issue that I am encountering with the page links in Webflow?

How can I fix the issue of not being able to add a customer domain to the "Publishing > Production" section on Webflow?

How can I merge a separate website into my main website in Webflow, including all content and animations, so that users can access it through the navigation menu?

Can Webflow host jQuery on its own CDN or allow users to deploy it from a more efficient location in order to improve page speed?

Is there a solution for automating the process of publishing a video on Youtube and automatically adding it to a Webflow CMS collection without having to manually update the collection list?

Does the white labeling feature in Webflow's pro plan apply to both the exported site and form submissions, or just the form submissions?

Are there any known solutions to address the issue of large dropdown menus being cut off and not being scrollable in the mobile menu on Webflow?

Can Webflow be connected to Lytics using the REST API?