SSL Certificate not installed

Technical Details

Forum version : #ModernBB
Position : Founder
Concerned browser(s) : Mozilla Firefox, Google Chrome, Internet Explorer
Who the problem concerns : All members
Forum link : ( link is hidden, you must reply to see )

Description of problem

Good morning,

I request an SSL certificate be installed on Friday at 20:48GMT and as yet it has not been installed.

The information in the admin panel does state that it can take up to 4 working days to apply the certificate, however the end of the 4th day is tomorrow, the certificate has yet to arrive, and brandon_g stated in this currently active thread that it takes 24 to 48 hours for your system to add the SSL ticket.

Would you please be able to check and confirm that the SSL certificate will be applied by the suggested deadline?

After you activated it, did you go back and set the options?

Thank you for the quick response.

I had not changed this setting and I have now. However, the certificate does not appear to have been obtained from a reputable and secure source (Edit: this statement is incorrect. The source is reputable https://letsencrypt.org/), as I am being hit with certificate domain errors in Edge, Chrome, and Firefox (and presumably every other browser as well).

Are you able to supply a certificate from an acceptable source?

It is working for me.  Clear your browser's cache and history.

Hello

it is working for me also ( tested in all browsers)

Clearing the browser cache seems to have resolved half of the problem, so thank you for that.

Currently the forumotion URL to the forum works as intended, but the custom URL https://www.alpha-legion.eu does not appear to be behaving. Given how these certificates work, I believe the custom URL needs to be present in the certificate in order for it to successfully validate.

Would you be able to check the custom URL and see if its still an issue only on my end?

Exactly the domain name needs to be installed before you install the certificate.

I did have some issues with CNAME resolution, which I did set-up prior to the installation of the SSL certificate. However, I am uncertain if the resolution issue was resolved before the creation of the certificate as I missed the setting to actually enable it!

Presumably I need to remove and re-add the certificate now that the custom URL is resolving correctly?

Edit: Not sure I can remove the certificate through the administration panel.

I'm dealing with the exact same issue right now.

https://help.forumotion.com/t157616-ssl-certification-and-https-issue#1092696

Let me know if this can help you figure it out, even though I haven't been able to figure something out myself.

Ritzy2K wrote:I'm dealing with the exact same issue right now.

https://help.forumotion.com/t157616-ssl-certification-and-https-issue#1092696

Let me know if this can help you figure it out, even though I haven't been able to figure something out myself.

I think we need to wait for forumotion to go in and re-create the certificates, as it doesn't look like the admin panel offers a re-creation option. At time of creation a certificate needs to contain all valid URLs and our custom URLs are missing from the certificates provided. Now, it could be that either we setup the SSL certificate before our custom URLs were ratified, or there is a bug in their system that doesn't include the custom URL when the SSL certificates are created. Regardless, manual intervention on their part is required.

Patience is a virtue and all that!

TaeraSindral wrote:

Ritzy2K wrote:I'm dealing with the exact same issue right now.

https://help.forumotion.com/t157616-ssl-certification-and-https-issue#1092696

Let me know if this can help you figure it out, even though I haven't been able to figure something out myself.

I think we need to wait for forumotion to go in and re-create the certificates, as it doesn't look like the admin panel offers a re-creation option. At time of creation a certificate needs to contain all valid URLs and our custom URLs are missing from the certificates provided. Now, it could be that either we setup the SSL certificate before our custom URLs were ratified, or there is a bug in their system that doesn't include the custom URL when the SSL certificates are created. Regardless, manual intervention on their part is required.

Patience is a virtue and all that!

Yes, our paid domain isn't included in the SSL certificate, we installed the certificate before the custom domain came online, so yes they have to do this, we cannot do anything from AP

Hello @TaeraSindral I have sent a Email to our team to ask if they can change this over for you.

I hope to get a reply back soon but please note this mat take up to 24 to 48hrs as we are really busy right now.

APE wrote:Hello @TaeraSindral I have sent a Email to our team to ask if they can change this over for you.

I hope to get a reply back soon but please note this mat take up to 24 to 48hrs as we are really busy right now.

Thanks very much! I'll mark this topic solved as soon as the certificate has been replaced.

I am not saying it will be done, what i was saying is i have asked if we can do it then i will get back to you if we can or not.

Hello @TaeraSindral I have been told that we change the address for you and now your forum should have the HTTPS address on your own domain name,

If you are still having a problem you need to clear browser cache the try again using your domain name.

If this is now solved please press the mark solved button found at the top of this topic.

APE wrote:Hello @TaeraSindral I have been told that we change the address for you and now your forum should have the HTTPS address on your own domain name,

If you are still having a problem you need to clear browser cache the try again using your domain name.

If this is now solved please press the mark solved button found at the top of this topic.

I can confirm that this has been rectified. However, just for the benefit of anyone else reading this, the HTTPS setting under the SSL configuration in the administration panel had been reverted back to plain old http. This will need to be set HTTPS before the certificate will be checked.