Fixed
Details
Assignee
UnassignedUnassignedReporter
Brad WoodBrad WoodPriority
BlockerLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Details
Details
Assignee
Unassigned
UnassignedReporter
Brad Wood
Brad WoodPriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Created 14 February 2019 at 18:20
Updated 8 May 2020 at 18:50
Resolved 20 January 2020 at 16:26
There are new SSL certs coming out that are not in Lucee's cacerts file. This means lucee can't connect to certain servers using these new SSL certs. A recent example I ran into used a brand new Goaddy cert and I had to manually add new trusted certs to the cacerts file in Lucee for cfhttp to make SSL connections.
This ticket is for an immediate fix to update to a recent cacerts file. After that is done, a long term solution needs to be put in place which is being discussed here:
https://luceeserver.atlassian.net/browse/LDEV-917