Hello,

I am installing SSL Certification on my Linux Centos Server. And I am trying the first Domains. It is almost working. But I have one strange problem. If I use a URL to the Site root (www) it comes as Secure. But if I use a URL to any internal directory it comes as Unsecure, depending on using www or a slash at the end.

Please try it in your Chrome Browser, but, clear its Cache memory between the tests. I have added SSL to 2 of our Sites:

segurosagro.com.br
multisites.com.br

And I created a simple directory called testredirect which has just an index.html file with an image.

1) segurosagro.com.br/testredirect

It comes as Unsecure.

2) segurosagro.com.br/testredirect/

It works, and comes as Secure.

3) www.segurosagro.com.br/testredirect

It also works, and comes as Secure.

In the same way:

1) multisites.com.br/testredirect

It comes as Unsecure.

2) multisites.com.br/testredirect/

It works, and comes as Secure.

3) www.multisites.com.br/testredirect

It also works, and comes as Secure.

My actual httpd.conf <virtualhosts> entries for segurosagro.com.br and multisites.com.br are as below. You will see that they are slightly different. This is due to tests I was doing trying to solve the problem:

#--------------------------------------------------------
# multisites.com.br
#--------------------------------------------------------
<virtualhost 66.226.75.86:80>
ServerAdmin webmaster@multisitesdominios.com.br
ServerName www.multisites.com.br
ServerAlias multisites.com.br
ServerAlias www.multisites.net.br
DocumentRoot /var/www/html/multisites/www
ScriptAlias /cgi-bin/ /var/www/html/multisites/www/cgi-multisites/
<Directory "/var/www/html/multisites/www/cgi-multisites/">
Options ExecCGI Includes
AllowOverride None
</Directory>
ErrorLog logs/multisites-error-log
TransferLog logs/multisites-access-log
#
#Redirection to https
#
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
</virtualhost>

#--------------------------------------------------------
# segurosagro.com.br
#--------------------------------------------------------
<virtualhost 66.226.75.86:80>
ServerAdmin webmaster@multisitesdominios.com.br
ServerName www.segurosagro.com.br
ServerAlias segurosagro.com.br
DocumentRoot /home/segurosagro/www
ScriptAlias /cgi-bin/ /home/segurosagro/www/cgi-segurosagro/
<Directory "/home/segurosagro/www/cgi-segurosagro/">
Options ExecCGI Includes
AllowOverride None
</Directory>
TransferLog logs/segurosagro-access-log
#
#Redirection to https
#
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
</virtualhost>

Thanks for any help.

Hi,

Visiting https://segurosagro.com.br, I get:
Same for the other site.
This happens because both certificates are issued for the hosts with the www at the beginning (www.segurosagro.com.br, www.multisites.com.br).
Since they are from Letsencrypt, you can re-issue them for both the www and non-www hostnames.

Regards

Hi, bathory,

Yes, this really makes sense. My technician will not be here for a couple of days. Based on the httpd.conf records I listed within this post, could you tell me please where must I implement what you told me to?
Thanks a lot.
Mario./

You don't have to do anything with the apache config files.

You (or your technician), must re-issue new certificates from Let’s Encrypt for both domains and for both hosts (with or without the www at the beginning) within each domain.

Assuming that your technician has installed certbot using defaults and you don't want to wait for him, you can run:
to create new certs for the 1st pair of hosts. Of course do the same for the 2nd pair.

Attn: before anything else, don't forget to backup apache config files (under /etc/httpd/conf.d) and/or letsencrypt files (/etc/letsencrypt).

After running certbot you need to restart apache for the changes to apply.


Regards