SSL Expired and Hasn't Auto-Renewed
Hello,
One of our Brizy Cloud sites is currently showing an invalid SSL cert error as the certificate expired yesterday and hasn't auto-renewed.
The site is: https://wills.winnsolicitors.com/
Thanks,
Amy
-
Hello Amy,
The CNAME record should have the "value" passionfruit14594725.brizy.site. Kindly sign into your domain control panel and check the CNAME Record.
0 -
Hi, I've passed the on to our IT team to update, so hopefully it'll fix the issue.
Thanks.
0 -
Morning,
Our IT team updated the DNS records on Thursday and everything is showing as correct in Brizy Cloud, however, the site is still returning a privacy error and an out-of-date SSL certificate.
0 -
Hello Amy,
The owner of the above project is marketing@win.......tors.com and this account does not have a Brizy Cloud Pro plan which is necessary for publishing using custom sub domain.
Kindly clone this project to your Agency account amy.thompson@.............co.uk which has available PRO licenses. Follow the procedure at Clone Entire Projects with URL in Brizy Cloud in under 15 seconds! . Please also update the CNAME Record of the domain as per the new brizy.site subdomain of the cloned project. Get back to us, if you continue to face the SSL issue after migrating the project.
0 -
Hello,
This hasn't been an issue previously - will the same problem occur when our other microsites SSL cert expires?
Also, when cloning the site, things like pop-ups don't carry over. Is there a quicker way to import those, or do we need to download them from the original site, upload them to the cloned version, and then relink every single thing that was previously linked to each pop-up?
Thanks
0 -
Hello Amy,
If a website's custom domain is added and SSL is already working well, it will continue to work without a PRO subscription. Since SSL is associated with custom domains, a PRO account is needed to fix the SSL issue.
The cloning process should migrate the popups, embed codes, Project Settings etc. You will need to redo just Email Notifications and reconnect custom domain after cloning.
0 -
Thanks,
This microsite was created in the same way as our other one, which has been live for much longer with no SSL issues. Will we likely encounter the same problem when that site's SSL expires on the 16th?
0 -
Yes, there is nothing to be concerned about as long as the SSL is operational. If the SSL breaks in the next ten or more years, you will require a PRO subscription to fix it.
You stated, "Will we likely encounter the same problem when that site's SSL expires on the 16th?" Is there anything unique about the 16th?
0 -
Hello, just to follow up on this...
As I said in my previous message, the 16th was when the existing SSL cert was valid until on our other microsite.
I can confirm that we have had the same issue here with the SSL neot autorenewing, despite it not being an issue previously.
I've followed the same steps above for that site, so once the DNS records have been updated/propagated to point to the new site, it should hopefully resolve the issue with the second microsite.
Similarly, another of our websites (which was created without our Brizy Cloud account) is also showing as not secure, with the SSL cert having lapsed in September.
I've checked the DNS records and they're showing as correct in our Brizy Coud dashboard.
This website is onengineering.co.uk
0 -
Hello Amy,
The onengineering.co.uk issue is not due to Brizy Cloud SSL. Currently your domain is pointing to a holding page by 123-Reg because you have enabled domain parking for it. To fix this issue, you must unpark your domain in your 123-Reg account.
As you can see at https://www.123-reg.co.uk/support/domains/how-do-i-point-my-domain-name-at-the-123-reg-holding-page/ you can park a domain by adding two A Records with the following IPs
- 13.248.213.45
- 76.223.67.189
The above two A records are added to your domain apart from the A Record pointing to the Brizy Cloud
To fix the issue, kindly sign into your 123-Reg account and delete the A Records with the IPs 13.248.213.45 and 76.223.67.189
0 -
Hello,
We've updated the DNS records to remove the parked A records, although we don't know how they've appeared as they haven't been added by anyone internally and the site was pointing to the correct DNS records yesterday (as per my previous screenshots).
The site is now no longer pointing to the 123-reg parked page, however is still showing an SSL error:
0 -
Hello Amy,
We have added the SSL certificate. Kindly check. You may need to reload the page on your browser to see the latest change.
0 -
Afternoon, Further to the above SSL issues, two of our Brizy Cloud sites are currently showing as not secure and don't appear to have an SSL cert attached to them: claims.winnsolicitors.com and officialinjuryclaimassist.com
0 -
Hello Amy,
Like I had discussed earlier, you will have to clone these two projects to your Agency account before the SSL issue can be resolved.
0 -
Afternoon, as per my previous message RE the claims.winnsolicitors.com site on the 17/12/24, the website had already been cloned and just required the DNS records updating, which has been done this week. The DNS records are showing as correct in our Brizy Cloud dashboard, but the SSL certificate has not been isued/attached to the site.
As for the other website (officialinjuryclaimassist.com), this was created within our Brizy Cloud account and is a new website so shouldn't need to be cloned.
Within our Brizy Cloud dashboard, these are the only two websites which are showing as HTTP:// and not https:// (with the exception of unpublished projects)
0 -
Hello Amy,
I am sorry for misunderstanding. We have fixed the SSL issue with https://www.officialinjuryclaimassist.com/ Kindly reload the page on your browser to see the latest change.
For https://claims.winnsolicitors.com/, kindly update the CNAME record to raspberry5600125.winns.com
0 -
Afternoon, thanks for updating that SSL.
On the claims.winnsolicitors.com DNS, that's showing as correct in our cloud dashboard and that the CNAME should be kingfisher...etc The previous (non-cloud) version of the site was using the raspberry... DNS record
0 -
Hello Amy
We have fixed the SSL issue with https://claims.winnsolicitors.com/. Kindly check
0 -
Brilliant, that's working again now. Thank you!
0
Please sign in to leave a comment.
Comments
19 comments