|
On Sep 13, 2021, at 12:26 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:
Make sure you check all Certificate Authorities, Server and Client
certificates and any user certificates. If I recall that's at least 3
different places in DCM you need to look.
On Mon, Sep 13, 2021 at 10:58 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
Had several expired ones. Got rid of all of them plus I changed the DCM--
password (as per a similar issue Pete H had back in 2019) and restarted the
HTTPS dependent servers. No change.
Also tried restarting the entire TCP HTTP server setup - no joy.
Jon Paris
On Sep 13, 2021, at 11:19 AM, Brad Stone <bvstone@xxxxxxxxx> wrote:are
Jon,
Check all your certificates and CAs for expired ones. Delete any that
expired. This is a known IBM bug that is VERY odd.delete
It doesn't matter if the CA or cert has nothing to do with your
application, this error creeps up from time to time, so you have to
every expired cert (client, server, user created) and CAs.wrote:
On Mon, Sep 13, 2021 at 10:05 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
list
Applied all the latest TR PTFs yesterday and today my HTTPS servers are--
all failing.
The message in the log is:
"The default key has an expired certificate or the password of key
database file has expired, error = 107."
Neither of which appear to be true as best I can tell. The DCMsays the
cert is good thru 2022 and it was all working immediately prior to the
update.
The problem only appears to affect HTTPS - all other web servers, web
services, etc. are all working OK.
Anyone seen this or got any ideas?
Jon Paris
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
