How to Remove an SSL Certificate From Apache

Before removing SSL — the SEO and browser reality

Step 1 — remove the 443 VirtualHost and cert paths:

1. Locate the site's SSL virtual host: ls /etc/apache2/sites-enabled/ (Debian/Ubuntu) or /etc/httpd/conf.d/ (RHEL family).
2. Disable the 443 block: a2dissite your-site-ssl (Debian) or comment out the VirtualHost in the conf file.
3. Remove the certificate file references — the SSLEngine, SSLCertificateFile and SSLCertificateKeyFile lines go with the block.
4. Delete the certificate itself if Let's Encrypt: certbot delete --cert-name yourdomain.com (merely disabling the vhost leaves certbot renewing a ghost).
5. Remove the HTTPS redirect rules from the port-80 block, or every visitor will hit a dead door.
6. Validate and restart: apachectl configtest (apache2ctl on Debian), then systemctl reload apache2.

Verify with curl -I http://yourdomain.com. The browser and SEO realities — and why staging and internal tools are the legitimate cases — follow below. The VPS server stack gives root for this; the visitor-facing Not secure warning is what you are choosing to accept.

Step 1 — remove the 443 VirtualHost and cert paths

Two practical notes on Apache: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.

Step 2 — delete the Let's Encrypt certificate (certbot delete)

delete the Let's Encrypt certificate (certbot delete). Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Step 3 — remove the HTTPS redirect rules

On VirtualHost :443, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 4 — configtest, restart, verify

configtest, restart, verify. Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Keeping port 443 open vs closed — the firewall decision

On certbot delete, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

When removal is right — staging, internal, migration

Free migration is offered subject to terms and approval. It is not an unattended button, and it is not a promise for every custom stack. Open a ticket with the current host login or a full backup, keep the old host online until you have checked the copy, and only then change DNS.