How to fix ssl not accessible on Squarespace

Steps for Squarespace

1. Squarespace automatically provisions a free SSL certificate (via Comodo/Sectigo) for all sites and keeps port 443 open — firewall configuration is not in your control.
2. Go to Home Menu → Settings → Security & SSL.
3. Ensure 'Secure (HTTPS)' is selected (not 'Insecure (HTTP)'). Toggle 'HTTPS Encryption' to ON.
4. Enable 'Automatic SSL Renewal' to prevent future certificate expiry.
5. For custom domains, confirm DNS is pointed to Squarespace per Settings → Domains. Certificate provisioning happens automatically within 72 hours of DNS propagation.
6. If the SSL status shows an error, click 'Troubleshoot SSL' on the same page or contact Squarespace Support.

## 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.