[FQuest Announcement] SSL/TLS Certificate availability for IRs

[Bob]

FutureQuest is very pleased to announce that you can now add your IRs to an existing Let's Encrypt Certificate, as was originally posted here:
https://FutureQuest.net/forums/showt...642#post186642

We have just made it easier for Account Holders to extend their Let's Encrypt Certificate to cover IRs

First you MUST already have a Let's Encrypt Certificate Installed for your Main Domain.

• Access your CNC then click on Certificate Manager in the left navigation: https://www.futurequest.net/GoToCNC/
  
• Click on "Update Let's Encrypt Certificate"
  
• Then select the domain's that you want covered under your Let's Encrypt Certificate. (The domains selected MUST be pointed at FutureQuest)
  
• Click on "Generate Let's Encrypt Certificate"
  
• If one of the Domains selected isn't pointed at FutureQuest the Certificate Generation will FAIL and you will see what domain failed.

If you don't already have a Let's Encrypt Certificate installed for your package you would first need to order one from your QuestAdmin login, https://www.QuestAdmin.net/

Currently when you Order a Let's Encrypt Certificate you can only order it for the Main Domain, and you would need to add any IRs from your CNC once installed, however we will be adding the ability to order a LE cert with IRs included eventually.

Note: If your main domain is not pointed at FutureQuest but you have IR(s) that do and you want a LE certificate to cover them, place an order for the Main Domain like normal, but add a Comment in the Order that the Certificate is to cover only IRdomain(s).

For those that have their own Private Certificates, ie... Verisign, GoDaddy, Thawte etc. If you get a new certificate issued that also covers your IRs you can update your Certificate from your CNC Certificate Manager by clicking on "Update certificate with certificate from a different CA"

As always if you have any questions or a problem please send an email to the Service Desk, Service@FutureQuest.net

One of those mid year presents

-Bob

[manfred]

Hi Bob,

I'm using a private certificate for my main account (and ohters) and I think the CNC cert manager is broken now. I don't see any certificate informations anymore

Kind regards,
Manfred

[Bob]

Hello Manfred,

I see what you are referring to and we will look into that and get back with you.

Thanks for the heads up,
Bob

[Bruce]

One of the incidental changes made to support this feature introduced a typo in the CNC cert manager. That is now fixed.

Can I put in a plea for:

1. Automated 60 sec FREE SSL installs of Google sponsored Lets Encrypt.

2. PHP 7.X

3. HTTP/2

4. Nginx

5. SSD

6. Varnish

7. More memory to satisfy my ever complaining cache plugin

OK - that is my Christmas wish list.

Respectfully - customer #37

[manfred]

Hi Bruce!

Yes, it's working again.

Thank you!

[Bob]

As an Update to being able to extend Let's Encrypt Certificates to cover your IRs...

If you are ordering a Let's Encrypt certificate for the main domain for the first time you can now also add any IR's that overlay that package as part of the initial order...

NOTE: Any domain that you include in the Let's Encrypt Initial Order must be pointed at FutureQuest. We cannot activate Let's Encrypt Certificates for any domain that is not currently pointed at FutureQuest.

From your Quest Admin login,
https://www.QuestAdmin.net/

• Click on "Place a New Order"
• Select "Secure Server (Let's Encrypt certificate)"
• Select the Main Domain for the package
• Select the main domain and any IR's you want included.
• Click "Continue" and just follow the instructions from there.

You also can still add an IR to an Existing Let's Encrypt Certificate as noted in the original post of this thread.

-Bob

[artemis]

Thank You!

[Slim]

Seeing this, I just tried it out and ran into some issues.

I had a cert for my main package (kirkbird.com) and tried extending it to an IR (mbirdsall.com) and immediately started getting 403s (You don't have permission to access ...) on this server.

So, I tried changing the cert to take the IR back off to get things running again, and got an error saying that the domain had been left off.

I'm off to check the logs to see if I can see what problem there might be, but I want to get things back on line as soon as possible.
Thanks,

[Slim]

Ok, I think I got it working, but not fully fixed.

I had an .htaccess file for my main package, which was rewriting to https:
I (backed up and) deleted the file, and I can get back on fine. With http: but not https:

The logs indicated something about
Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden: ...