How to fix ssl not accessible on Magento Open Source

Steps for Magento Open Source

1. Follow the same server-level steps as Adobe Commerce above (open port 443, install TLS certificate via Certbot or hosting panel).
2. In Admin → Stores → Configuration → General → Web → Base URLs (Secure), update the Secure Base URL to https://.
3. Set 'Use Secure URLs on Storefront' and 'Use Secure URLs in Admin' to 'Yes'.
4. Add a redirect in your Nginx or Apache config: for Nginx, add `return 301 https://$host$request_uri;` in the port-80 server block; for Apache, add `RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]` in your VirtualHost or .htaccess.
5. Flush the Magento cache: `bin/magento cache:flush`.

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