Ingestion is failing after replacing an expired SSL cert.

[mike-credisense]

We are getting a "SSL Connection could not be established, an existing connection was forcibly closed" from Serlilog after updating an expiring SSL Certificate.

The certificates was installed and rebound to the urls
The front end works but not the ingestion port

[KodrAus]

Hi @mike-credisense 👋 Is this all resolved now?

You might find some details by checking Seq's ingestion log under Settings > Diagnostics > Ingestion Log. Otherwise if you send us a diagnostic report from that same screen we'll take a look.

[mike-credisense]

Yes all resolved now Mike Wemyss Security and Technical Analyst Credisense Limited +64 (0) 212579516 | ***@***.******@***.***> | credisense.co.nz<http://credisense.co.nz/> ISO/IEC 27001:2013 | ISO/IEC 9001:2015 | Certificate No.NZP1107CA From: Ashley Mannix ***@***.***> Sent: Monday, August 19, 2024 10:29 AM To: datalust/seq-tickets ***@***.***> Cc: Mike Wemyss ***@***.***>; Mention ***@***.***> Subject: Re: [datalust/seq-tickets] Ingestion is failing after replacing an expired SSL cert. (Discussion #2250) Hi @mike-credisense<https://github.com/mike-credisense> 👋 Is this all resolved now? You might find some details by checking Seq's ingestion log under Settings > Diagnostics > Ingestion Log. Otherwise if you send us a diagnostic report from that same screen we'll take a look. — Reply to this email directly, view it on GitHub<#2250 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVH24PLICXVRJEV44BSHU7DZSEN35AVCNFSM6AAAAABMWXBKSGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZXGYZDONA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>