The original post: /r/usenet by /u/3F6B6Y9T on 2024-10-03 12:02:15.

About 24 hours ago, my client started reporting a certificate failure for usenet.farm - upon checking, it expired back in January (!!!), but my client only started reporting issues yesterday. A little odd to say the least.

Anyone else seen/seeing this? Or had any response from the provider?

openssl s_client -servername news.usenet.farm -connect news.usenet.farm:443| openssl x509 -noout -dates
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = news.usenet.farm
verify error:num=10:certificate has expired
notAfter=Jan 28 06:12:41 2024 GMT
verify return:1
depth=0 CN = news.usenet.farm
notAfter=Jan 28 06:12:41 2024 GMT
verify return:1
notBefore=Oct 30 06:12:42 2023 GMT
notAfter=Jan 28 06:12:41 2024 GMT

Initially it was about 50/50, but today it’s more like 90% expired with 10% not - so presumably it’s some nodes in a pool:

openssl s_client -servername news.usenet.farm -connect news.usenet.farm:443| openssl x509 -noout -dates
depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
verify return:1
depth=1 C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA Domain Validation Secure Server CA
verify return:1
depth=0 CN = news.usenet.farm
verify return:1
notBefore=Nov 17 00:00:00 2023 GMT
notAfter=Nov 17 23:59:59 2024 GMT

I know I can bypass certificate checking, but I’m not sure I want to!