How to fix ssl not accessible on Webflow

Steps for Webflow

1. Webflow automatically provisions free SSL certificates and manages port 443 for all sites hosted on Webflow's infrastructure.
2. In Webflow Designer, go to Project Settings → Hosting.
3. Ensure your custom domain is added and DNS is configured as instructed (A record or CNAME per Webflow's dashboard guidance). Webflow will auto-provision the certificate.
4. Confirm 'HTTPS Redirect' is enabled in Project Settings → Hosting → Custom Domain section — this ensures port-80 traffic redirects to 443.
5. If you see an SSL error, remove and re-add the custom domain in Project Settings → Hosting to trigger re-provisioning.
6. For Webflow sites exported and hosted on your own server, open port 443 in your server firewall and install a TLS certificate (see generic steps).

## Nginx — minimal HTTPS server block with HTTP redirect

server {
    listen 80;
    server_name yourdomain.com www.yourdomain.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    server_name yourdomain.com www.yourdomain.com;

    ssl_certificate     /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    ssl_protocols       TLSv1.2 TLSv1.3;
    ssl_ciphers         HIGH:!aNULL:!MD5;

    # ... rest of your config
}

What is ssl not accessible?

Every website that uses HTTPS — the padlock in the browser address bar — communicates over TCP port 443. When port 443 is closed or unreachable, your store cannot serve any encrypted traffic at all: visitors get browser security warnings, payment flows break, and search engines may refuse to index your pages. An SSL/TLS certificate is the digital credential that makes this encrypted connection possible, and port 443 is the network "door" it must be delivered through. If that door is shut, HTTPS simply does not work, regardless of whether you have a certificate installed.

Google has used HTTPS as a ranking signal since 2014, and a store that is unreachable over HTTPS will be demoted or deindexed entirely — costing you organic traffic and revenue. Modern browsers (Chrome, Firefox, Safari, Edge) display a full-page "Not Secure" or "Connection Refused" warning when port 443 is blocked, causing shoppers to abandon immediately and destroying conversion rates. Payment card industry rules (PCI-DSS) require all cardholder data to be transmitted over encrypted channels; without HTTPS you are non-compliant and risk losing the ability to accept card payments. Under privacy regulations (GDPR, CCPA), transmitting customer data unencrypted is a reportable data breach waiting to happen.

See the complete Ssl not accessible guide for every platform and the full background.