Ssl not accessible

What it is

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.

Why it matters

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.

How to fix it

1. Confirm the problem: use an online port-checker tool (e.g., ping a service that tests port 443 on your domain) or run `curl -I https://yourdomain.com` from a terminal to see whether you get a certificate handshake or a connection-refused error.
2. Identify where port 443 is being blocked: the block can be at (a) your hosting server's firewall/security group, (b) a network-level firewall at your data centre, or (c) a CDN/proxy layer in front of your site. Check each layer.
3. Open port 443 in your server or cloud firewall: for a VPS or dedicated server, update your firewall rules (e.g., `ufw allow 443/tcp` on Ubuntu, or the equivalent iptables rule); for cloud hosting (AWS, GCP, Azure), open port 443 in the instance's Security Group or Firewall Rules.
4. Verify a valid SSL/TLS certificate is installed and bound to port 443: if no certificate exists, provision one (free via Let's Encrypt / Certbot, or through your host's control panel) and configure your web server (Nginx, Apache) to listen on port 443 with that certificate.
5. Confirm HTTP-to-HTTPS redirection is active so all traffic on port 80 is permanently redirected (301) to port 443, preventing any accidental plain-text access.
6. Re-test end-to-end: visit https://yourdomain.com in a browser and confirm the padlock appears; run an SSL checker (e.g., SSL Labs) to verify the certificate chain is valid and the port is open.

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

Fix it on your platform

Pick your platform for the exact steps.

Frequently asked questions

Authoritative references

• OWASP Top Ten — OWASP
• OWASP Cheat Sheet Series — OWASP
• HTTP Strict-Transport-Security (HSTS) — MDN
• Website security — MDN