Performed steps but now SSL not installed

Help
98

Already deleted that cert, just debugging from where all those redirects are coming from , or which file got those redirects to happen is mind boggling, thought it was easy when we first got certbot + letsencrypt , but as we see now is just waste of time. sorry for those words, but it is easy to go with managed servers rather then take matters in your own hands lol. :grinning:

1 Like
99

Whatever for?
You are not going in a direction that will get you to where you want to be.

4 Likes
100

If we have to debug 1 problem for 2 days , we are going to loose all the directions anyways, it was so blurry looking down the road LOL :grinning: :grinning:

Going very well without installing SSL and certbot , but as soon as we installed those programs, we got into trouble and finding no way to get out of the situation.
We also cannot go without SSL for sure.

2 Likes
101

I hope this other path can get you where you need to be.

Cheers from Miami :beers:

3 Likes
102

Cheers mate, stay well and have a nice time. :dark_sunglasses: :guitar:

2 Likes
103

Just a quick question: how would you install said bought certificate?

In the above posts I see a lot of Apache configuration and certbot configuration checks, whereas this problem ultimately probably is due to a Content Management System redirecting back from HTTPS to HTTP. For example, Wordpress has a hand of doing this if it isn't configured properly.

The solution probably was to disable the HTTP to HTTPS redirect, set up by certbot, fix the CMS so that HTTPS doesn't redirect back to HTTP and afterwards re-install the HTTP to HTTPS redirect.

4 Likes
104

Easier said then done.

1 Like
105

I'm just afraid you're going to run into the same problem you were having just now.

4 Likes
106

Let's see, we cannot say the same, until we try a different approach, hoping for the best

1 Like
107

Is there any other way of installing SSL with Certbot + Letsencrypt workaround
may be adding some settings to apache virtualhost <virtualhost *:443> ?

A fresh installation

1 Like
108

So the other path did NOT solve your problem?
Do you clearly understand the problem you are facing?
Are we now going back on the original path and set to, as you put it, "waste" even more time?

3 Likes
109

It's perfectly possible to get just the certificate with certbot and install it manually.

4 Likes
110

@rg305 we have not yet chosen or tried other path, just giving it one more try to install certificate successfully from a different point of view/angle, before actually going for another path.

1 Like
111

Enjoy your path(s).
But I think I have nothing more to offer you.

3 Likes
112

Thanks for the clarification @rg305

1 Like
113

With certbot certonly --apache, certbot will only get the cert and not install it automatically into Apache. So that leaves you the chance to do that manually.

4 Likes
114

Yes, but if we do it with letsencrypt, it will give us so many redirects + Apache

1 Like
115

If we have to give the document root in <virtualhost*:443>
what will be the root directory in apache?

Is it the same root directory for <virtualhost*:80> ?

1 Like
116

I'm afraid you don't fully grasp the different elements involved in the current process. Let me explain the different elements/names in the most simple way as possible:

  • Let's Encrypt: a Certificate Authority (CA) which issues certificates through an automated process called "ACME". Let's Encrypt offers an ACME "API" to get certificates issued through a so called "ACME client";
  • certbot: a very comprehensive ACME client which can:
    • automatically retrieve and install a certificate into a webserver; but also:
    • just get a certificate without installing it automatically into a webserver, but also:
    • automatically redirect HTTP to HTTPS by modifying the webserver configuration, but also:
    • NOT modify any webserver configuration file, so no redirect from HTTP to HTTPS.

So to conclude: with certbot you get a Let's Encrypt certificate issued where you have many options which include fully automated webserver integration but also no webserver integration at all.

The Let's Encrypt certificate by itself CANNOT cause any redirect errors. That's due to webserver configuration issues, which can be caused by something automated by certbot, but you're not obligated to have certbot modify your webserver configuration. You can choose not to.

4 Likes
117

We have chosen no webserver integration and will have to do it manually

1 Like