Cargo cannot download dependencies - ssl

I'm trying to build local Rust projects with dependencies from various crates using Rust 1.35.0 on Windows 10 x64. Every time I try to run cargo build or cargo run the following error message appears.
error: failed to download from `https://crates.io/api/v1/crates/nom/5.0.0/download`Caused by: [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.)
I've tried this with several other crates apart from nom and got exactly the same error message with exception of crate name and version. Reading around pointed me to disabling my firewall, this does not work.
How can it be solved.

Related

Unable to create quarkus project on intellij

Getting the following error:
Initialization failed for 'https://code.quarkus.io' Please check URL, network and proxy settings. Error message: Cannot download 'https://code.quarkus.io/api/extensions': code.quarkus.io
Can't figure out where to start with this issue

Ethereum: Error: *** Deployment Failed *** "Migrations" -- invalid sender

I am trying to deploy a smart contract on a private blockchain on ethereum network. But it gives me this error" Error: *** Deployment Failed ***
"Migrations" -- invalid sender."
Now I have done some reading and saw the problem is with the version of "truffle hdwallet provider".
This is the response that I get after installing npm inside directory which shows that hdwallet is installed but still i get this error.
Even if i install another version of hdwallet provider I get the same error as seen below:
I dont understand what am i missing here. If someone can help i will be greatfull. Thanks
Problem solved. It was not actually the problem with truffle hdwallet but the version of truffle. Truffle 5.2.6 was giving me that error and it works fine with truffle 5.0.0.

Sonatype Nexus upload fails with Certificate for nexus.xyz.corp doesn't match common name of the certificate subject: wiki.xyz.corp

I get the following error when trying to upload files to Nexus using Gradle:
Certificate for doesn't match common name of the certificate subject: wiki.xyz.corp
Details:
C:\data\Workspaces\httpstest>gradlew uploadArchives
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar SKIPPED
:uploadArchives
Could not transfer artifact com.xyz:httpstest:jar:1.0.0 from/to remo
te (https://nexus.xyz.corp/nexus/content/repositories/1st-rel/): Cer
tificate for <nexus.xyz.corp> doesn't match common name of the certi
ficate subject: wiki.xyz.corp
Could not transfer artifact com.xyz:httpstest:pom:1.0.0 from/to remo
te (https://nexus.xyz.corp/nexus/content/repositories/1st-rel/): Cer
tificate for <nexus.xyz.corp> doesn't match common name of the certi
ficate subject: wiki.xyz.corp
:uploadArchives FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':uploadArchives'.
> Could not publish configuration 'archives'
> Failed to deploy artifacts: Could not transfer artifact com.xyz
:httpstest:jar:1.0.0 from/to remote (https://nexus.xyz.corp/nexus/co
ntent/repositories/1st-rel/): Certificate for <nexus.xyz.corp> doesn
't match common name of the certificate subject: wiki.xyz.corp
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.
BUILD FAILED
Total time: 5.511 secs
Downloading via HTTPS works fine, but uploading does not.
The certificate for nexus.xyz.corp has the correct common name, and NOT wiki.xyz.corp as the error message implies.
However, wiki.xyz.corp is a different site running on the same server.
What's the problem here?
This occurs when the different domains (wiki.xyz.corp and nexus.xyz.corp) are shared using SNI.
It occurs at least in versions Gradle 2.5 - Gradle 2.13. The reason is that Gradle uses the Maven Wagon Library in a version that does not support SNI. In this case, the webserver returns a default certificate. It seems, that wiki.xyz.corp was defined as default certificate.
This is discussed in Gradle Discussion and Gradle Issues.
Possible workarounds:
Define nexus.xyz.corp as default certificate, but beware of problems on the other site
Replace Maven Wagon with Maven Publish, but this is currently in beta. See Maven Publish.
try to configure your system without SNI
start Gradle in a way that host checking is disabled (this is a security leak!):
gradlew -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true uploadArchives

Cargo start up error

I am running 'mvn clean install -Dmaven.test.skip=true' command for a web application. but it gives following error. I set the catalina home as an environment variable. i am using maven 3.1.1 version. Please help me
FATAL ERROR in native method: JDWP No transports i
nitialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[WARNING] [talledLocalContainer] ERROR: transport error 202: bind failed: Addres
s already in use
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:star
t (start-container) on project RCMigrationWebApp: Execution start-container of g
oal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:start failed: Failed to start t
he Tomcat 7.x container. Deployable [http://localhost:8080/cargocpc/index.html]
failed to finish deploying within the timeout period [120000]. The Deployable st
ate is thus unknown. -> [Help 1]
Probably you have to kill any process running at 8080, looks like the port is already in use..
ERROR: transport error 202: bind failed: Address already in use
Port in use. Run netstat -bv if you are using Windows. You will get to know which process is holding up the port. With your stackTrace, it looks very obvious.
Let me know if it helps.

Build using gradle in cmd fail

Error message
Error listing versions of com.android.tools.build:gradle:0.4+ using class org.gradle.api.internal.artifacts.repositories.resolver.MavenVersionLister$1. Will attempt an alternate way to list versions. This behaviour has been deprecated and is scheduled to be removed in Gradle 2.0
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'TestMain'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not resolve com.android.tools.build:gradle:0.4+.
Required by:
:TestMain:unspecified
> Failed to list versions for com.android.tools.build:gradle:0.4+.
> Could not list versions using M2 pattern 'http://repo1.maven.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]
'.
> Could not GET 'http://repo1.maven.org/maven2/com/android/tools/bui
ld/gradle/'.
> Connection to http://repo1.maven.org refused
Am i using incorrect sdk?
You can follow the this tutorial.
http://www.vogella.com/articles/AndroidBuild/article.html
Then turn off your firewall and antivirus software.