Anyone else getting subversion SSL expiration notifications today?

[Greg O'Lone]

Starting yesterday or today we've started getting notifications on our materials that say:

--- EXIT CODE (1) ---

--- STANDARD OUT ---
<?xml version="1.0" encoding="UTF-8"?>
<log>
--- STANDARD ERR ---
STDERR: svn: E170013: Unable to connect to a repository at URL 'https://.....'
STDERR: svn: E230001: Server SSL certificate verification failed: certificate has expired
---

I removed the svn ~/subversion/auth configuration and reconnected at the command line but it doesn't solve the material problem inside gocd. 

Thoughts?

[Ashwanth Kumar]

Wild thought, Could it be related to this ongoing issue on Sectigo root CA expiring on May 31? 

https://www.reddit.com/r/linux/comments/gshh70/sectigo_root_ca_expiring_may_not_be_handled_well/

Quoting from the thread on reddit. 

> It looks like some older distributions of linux (we've seen issues with Deb 9 and earlier and Ubuntu 16.04 and earlier) will not properly expire/ignore this root cert unless it is actually removed. Ubuntu 18 and up, as well as Deb 10 are unaffected.

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/93b86c88-83eb-4566-ba9b-ca80b4d9df9b%40googlegroups.com.

--

Ashwanth Kumar / ashwanthkumar.in

[Greg O'Lone]

Yeah, that was it. Now I just need to figure out why we can't upload artifacts.