Your exact error should identify exactly which URL is having a problem with SSL.
It might be on your end, it might be on the Server side.
If necessary,
At least temporarily you should be able to avoid the issue by changing the repo URI from “https” to “http”
Of course that has many implications regarding security accessing and encrypting the connection, but to a large degree is not the usual severity because your system will still authenticate the repo using GPG keys by default.