How to fix ssl not accessible on WooCommerce

Steps for WooCommerce

1. WooCommerce runs on WordPress, which runs on your own hosting — you (or your host) control port 443.
2. Log in to your hosting control panel (cPanel, Plesk, or your host's dashboard) and navigate to the SSL/TLS section.
3. Install a free Let's Encrypt certificate: in cPanel go to Security → SSL/TLS → Let's Encrypt™ SSL (or use the 'SSL/TLS Status' tool); click 'Issue' next to your domain.
4. Ensure your hosting firewall / server security group has port 443 open. In cPanel, check Security → ModSecurity or contact your host to confirm port 443 is not blocked at the network level.
5. In WordPress Admin → Settings → General, change both 'WordPress Address (URL)' and 'Site Address (URL)' to https://.
6. Install the 'Really Simple SSL' plugin (free, WordPress.org repository) to handle HTTP→HTTPS redirects automatically and fix mixed-content issues.

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