Hello All
I have just received word, it should be ok now.
You can all try logging on.
A couple minutes after your message website working as expected 
This really isn’t a good look for Quickfile.
I’ve just moved over from Sage which was an absolute clownshow.
It would be good to see this resolved asap.
Now working for me. Thanks @QFSteve
I’m just saying that the actual risk from an expired certificate isn’t as black and white as the browsers might suggest. A day or two out of date is a lot less likely to be dodgy than months or more past expiry. A shorter lived certificate is better than a long lived one even if both are technically in date.
I don’t see it as a particularly big deal but are you able to explain how it happened?
Can the certificate not be set to auto-renew?
Thx for sorting it so quickly.
Regards
Michael
And there it is, solved in next to no time.
My other ‘provider’ left me two weeks without the ability to send invoices.
clear your cache/cookies or close your broswer
I think you misread. My post says:
Emphasis added on word I think you misread as “Not”
Manual renewal was the default for decades.
There are modern services that handle auto-renewal of certificates, but they weren’t the norm back when Quickfile launched in 2010.
Still seeing the insecure message this morning?
If you manually bypassed the warning in order to get to your QuickFile while the certificate was expired, then your browser has likely remembered the fact that you set a security exception for this site and you’ll have to reset that flag. If you click on the “not secure” button there should be something in that popup to “remove the exception” or “turn security warnings back on” or some such wording.
Hi @Account
What browser and device are you using, please?
Windows 11 pro - latest version of chrome.
Thank you. It seems that something external on the site is preventing it from being secure, as the certificate is valid. This could be an extension installed on Chrome, for example, or something loading in the background. It all looks OK on this end, so I’d like to take a further look.
Can you please go to the page you’re seeing the secure error, and then three dots in the top right corner on Chrome, go to More Tools and select Developer Tools and click on the Security tab across the top?
Lastly, leaving this window open, refresh the page by pressing F5 wile viewing the page, or clicking the refresh icon. This should then refresh the developer tools and highlight any insecure connections.
I was about to do this and noticed the insecure error has now gone away.