Added SSL Certificate to my Subdomain, it is work HTTPS but not HTTP

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: compliance-test.ilensys.com

I ran this command: sudo certbot --apache

It produced this output:
output screenshot attached.

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

ubuntu@ip-172-18-2-73:~$ certbot --version
certbot 1.15.0

with https it is working fine. URL: https://compliance-test.ilensys.com/
image

with http it not working fine. I'm not getting the lock symbol. URL: http://compliance-test.ilensys.com/

image

Please help me on this issue.

Thanks & Regards,
Abdul Hadi

1 Like

Hi @AbdulHadi

that's expected. http is never secure -> always no lock symbol.

That's not a problem, that's the result of a missing encryption.

PS: You should add a redirect http -> https.

1 Like

@JuergenAuer, Thanks for the update.

Can you please share the standard document of redirect http -> https.

so that i will follow that document and configure it.

Thanks & Regards,
Abdul Hadi

The output from Certbot is warning that your configuration uses the Apache RewriteRule directive to rewrite URLs on your site, in a way that might conflict with Certbot's attempts to use RewriteRule to forward HTTP to HTTPS. Since Certbot tried to do this but it isn't working, it probably does conflict.

Here is the documentation for this part of Apache:

https://httpd.apache.org/docs/current/mod/mod_rewrite.html

Hopefully whoever created the pre-existing RewriteRule can understand the interaction between this and Certbot's added RewriteRule and find a correct way to combine them so they behave as desired.

If you're not sure how to proceed, you should post your Apache configuration here (use ``` before and after the pasted configuration so that the forum displays it as code) and someone familiar with this may be able to advise you.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.