[AtmoVantage]

Ever since September 30th my custom S3 connection has stopped working for my website sync. It says that the certificate has expired: “Error! Application was unable to connect to your server: certificate has expired”

I have several other applications that use this same custom S3 gateway and they are not having any problems. I assume this is related to the Global Let’s Encrypt certificate that recently expired. I’m trying to figure out if this is an issue with my local machine or if the certificate used by Publii itself is actually expired and needs to be renewed?

 

 

[Tomasz Dziuda]

Hi,

It seems that Electron has a bug which causes that cross-signed certificates where one of the cross-signed certificate is invalid causes the whole certificates chaing to be invalid.

https://github.com/electron/electron/issues/31212

https://community.letsencrypt.org/t/issues-with-electron-and-expired-root/160991

At this moment the only fast solution is to generate certificate which does not contain invalid certificates in the chain.

We will try to release an update next week which will address this issue (as I see electron released updated versions, but we need to upgrade electron so it will be a task which needs additional tests).

--
Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

[AtmoVantage]

Hi Tomasz, thanks for the reply and appreciate the additional information. Glad to hear that this bug was reproduced and that it wasn’t just an issue with my system! I look forward to downloading the hotfix in due time.

[Author]

Posts