From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

TLS version error.  perhaps you are running on an older version of Java, or have a proxy in-between?

could you paste the error msg pls? (screenshots are hard to process)

``` Could not resolve io.reactivex.rxjava3:rxjava:3.1.5.
         &gt; Could not get resource '<https://repo.maven.apache.org/maven2/io/reactivex/rxjava3/rxjava/3.1.5/rxjava-3.1.5.pom>'.
            &gt; Could not HEAD '<https://repo.maven.apache.org/maven2/io/reactivex/rxjava3/rxjava/3.1.5/rxjava-3.1.5.pom>'.
               &gt; The server may not support the client's requested TLS protocol versions: (TLSv1.2, TLSv1.3). You may need to configure the client to allow other protocols to be used. See: <https://docs.gradle.org/7.5.1/userguide/build_environment.html#gradle_system_properties>
                  &gt; PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  ```

presumably you have a proxy configured in-between Gradle and Maven central.  Check that configuration - it may not support HTTPS or otherwise require special setup.

Or it plays mitm and replaces real certificates with its own. Or you have some "antivirus suite" that does the same

If browser opens <https://repo.maven.apache.org/maven2/io/reactivex/rxjava3/rxjava/3.1.5/rxjava-3.1.5.pom> correctly check the cert chain there and look if it has _GlobalSign_ as a root CA

If you don't find which of your parts are failing, you might need to set `javax.net.debug` system property to `all` to get the SSL debug output and find out what is going wrong with the HTTPS communication.

`isAllowInsecureProtocol` only helps if you want to use HTTP, not if the HTTPS communication is broken.

&gt; I've imported the certs as well
In the JDK's truststore? Depending on the JDK and how it was installed, it might or might not use the system's truststore.

…and which certs?  the certs for Maven Central are already trusted by stock JDKs.

<@U02S31Y7J2K> - <https://services.gradle.com>

??? that’s a wholly different URL &amp; Thing than the error from Gradle.

it started with that... and ended with the <https://repo.maven.apache.org>

The error is on resolving artifacts from `<https://repo.maven.apache.org>`

Perhaps there are some proxy/firewall settings or something that I cannot view. For now, I am moving by manually adding the dependencies to the project. I will continue to check this issue on the side... Thank you all:pray: