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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Domain1.com is naturally setup in a sub-directory called “site/domain1.com”, and no extra work is needed.
In the case of domin2, the directory is called “site/domain2.com” but using the redirection file in “sites/sites.php” I internally change “new.domain2.com” to “domain2.com” using the line: “$sites['new.domain2.com'] = 'domain2.com';”
So far everything works just fine the redirection from new.domain2.com to domain2.com is done by “sites/sites.php”.
Now I wanted to install let’s encrypt on both domains.
In trying to assess the problem with my limited knowledge, I believe that the redirect used by Drupal and the redirect used by “certbot” are conflicting or simply not playing nice.
What I am seeking is help in debugging or solving this or someone pointing me to a similar problem solved by others or at least a good article explaining the redirecting system used by let’s encrypt and Drupal.
This would be ten times easier if you would just answer all the questions.
Namely:
That is NOT a domain; that is a persons name.
And again with random "example" information.
So the best we can do, at this point, is to just guess...
Well, I guess that you are using Apache and it is a real mess.
It runs, but only because it is quite difficult to "configure" apache in a way that it will NOT run.
That doesn't make it "right" it just means it is trying its' best to understand what you want it to do.
But don't take my guess as fact.
Try something that might shed some light on the presumed "mess": apachectl -S
Then I also guess that your cert has only one name.
So when you access the same vhost config (back to the messy configuration) via more than that one "correct" name the others return the insecure connection warning.
But I could be completely wrong.
I mean I am only guessing here...
I was hoping to avoid getting into Apache, vHost and Name based server as I had everything working in Drupal using a single file called sites.php, but it looks like I will have to learn it all before I can continue with multiple sites on one server.
However, since “hobbygap.com” is a future project, my “perot.org.il” is my concern at the moment and since it’s almost working all I have to fix is: to direct HTTP to https.
I wonder if you have a simple suggestion on how to correct this? (before I get deep into Apache.)