ibrowse with certificate issue

[ib maillist]

Hello Oliver and All,

ibrowse presents an amissl related requester when trying to access www.seagate.com using https

the requeater says unable to get local issuer certificate

looking at the certs that comes with the amissl package, when comparing to the bundle included with a recent installation of firefox, it seems the Comodo root AAA certificate services certificate is missing in the bundle that comes with latest amissl v5.26 update.

I cannot tell with certainty if the issue in ibrowse with the above site, is directly related to the missing certificate or not, this particular site use a chain of certificates, and the topic in itself is quite complex.

many thanks to Oliver for supplying the amissl updates, it is very much appreciated,

rgds,

-listmail

[Oliver Roberts]

On Thu, 5 Feb 2026 at 12:19, ib maillist <list...@nospammail.net> wrote:

Hello Oliver and All,

ibrowse presents an amissl related requester when trying to access www.seagate.com using https

the requeater says unable to get local issuer certificate

looking at the certs that comes with the amissl package, when comparing to the bundle included with a recent installation of firefox, it seems the Comodo root AAA certificate services certificate is missing in the bundle that comes with latest amissl v5.26 update.

I cannot tell with certainty if the issue in ibrowse with the above site, is directly related to the missing certificate or not, this particular site use a chain of certificates, and the topic in itself is quite complex.

Yes, the error is ultimately due to the missing certificate. However, the certificate is missing for a good reason. Mozilla removed the trust bit on the certificate in April 2025, due to it using old algorithms deemed insecure, hence since then it has not been part of the Curl cert bundle (which AmiSSL uses), as Curl uses the Mozilla cert bundle minus distrusted certificates.

The problem is with Cloudflare, which Seagate is using. They need to update their SSL configuration on Cloudflare to ensure their domain uses the latest certificate chains, and not this old outdated one (which Cloudflare are still using today!).

For example: https://community.cloudflare.com/t/cloudflare-ssl-trust-chain-ends-with-invalid-root-ca-aaa-cerificate-services/843576/15 

--

 Oliver Roberts  /  @Futaura  /  www.futaura.co.uk

[ib maillist]

Thankyou for the clarification, then it all makes good sense,

have a nice weekend,

rgds

-listmail