Failure installing sbt: "Server access Error: java.security.cert.CertificateException:" - sbt

When I try to install error messages, it fails to download. I get error messages like this:
[error] Server access Error: java.security.cert.CertificateException: No subject alternative DNS name matching repo.scala-sbt.org found. url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-pgp/scala_2.10/sbt_0.13/0.8.3/ivys/ivy.xml
I can confirm, when accessing via my browser, that the certificate installed for the domain repo.scala-sbt.org is actually the certificate for repo.typesafe.com, and this seems to be the source of the error. It doesn't appear to be a DNS issue as http://repo.scala-sbt.org/ (insecure) works.

Please see https://github.com/sbt/sbt/issues/2125 for the workarounds. Specifically "http" should not be used.
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
Edit: This issue is now resolved. No workarounds should be required.

As a temporary workaround, add the file ~/.sbt/0.13/plugins/temp.sbt with the following contents:
resolvers += Resolver.url("fix-sbt-plugin-releases", url("https://dl.bintray.com/sbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)
You'll still see the error, but sbt will be able to find the dependency for which it is searching when accessing https://dl.bintray.com/sbt/sbt-plugin-releases directly (the place to which repo.scala-sbt.org presently redirects).

Upgrading nss package on CentOS worked for me.
sudo yum upgrade nss

Related

Failed upload of Conan package to Artifactory server when revisions are disabled

Im trying to upload a conan package to a remote Artifactory server. I want revisions to be disabled so I use CONAN_REVISIONS_ENABLED=0. However I get the following error:
ERROR: 404 Client Error: Not Found for url: https://<SERVER>/artifactory/api/conan/<SERVER_ALIAS>/v1/files/<PACKAGE>/0/export/conanfile.py
If I set CONAN_REVISIONS_ENABLED=1 the upload works fine. The server is configured for local repositorys (virtual or remote repos does not exists) so the APIv1 should work.
Is there a configuration on the server side that I have missed that might cause this error?
Artifactory version is: 6.13.1
Repository layout is: conan-default
For the background to this question see this issue on github.

Cause: org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl

I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0

aodh-api service not getting installed after devstack installation

I'm trying to install aodh. I am following this tutorial - https://docs.openstack.org/aodh/stein/install/install-ubuntu.html
When I run this command
aodh alarm list
I'm getting following error.
<html>
<head>
<title>503 Service Unavailable</title>
</head>
<body>
<h1>503 Service Unavailable</h1>
The server is currently unavailable. Please try again at a later time.<br /><br />
The Keystone service is temporarily unavailable.
</body>
</html> (HTTP 503) (Request-ID: req-9f8035a5-e324-4e2f-b3f0-037b68f88d1a)
Even though the error says keystone is unavailable, I highly suspect that already there was some problem with aodh installation.
From the aodh link above, I in the final step, it says:
Restart the Alarming services:
# service aodh-api restart
# service aodh-evaluator restart
# service aodh-notifier restart
# service aodh-listener restart
When I tried this
service aodh-api restart
I got following error
Failed to restart aodh-api.service: Unit aodh-api.service not found.
Moreover in step 2 of above link
Source the admin credentials to gain access to admin-only CLI commands:
$ . admin-openrc
Since, I was unable to find admin-openrc, I skipped that step.
So, I am thinking probably aodh installation didn't go well. Hence the aforementioned error in 'aodh alarm list' command.
Other commands like 'nova list' etc are running fine
Can someone please help in figuring out, what could be going wrong?
Install aodh component as plugin during devstack installation.
https://ask.openstack.org/en/question/116895/how-to-configure-devstack-with-ceilometer-gnocchi-and-aodh-components/
Recently, I encountered this problem, which has been answered on the official website.
https://docs.openstack.org/aodh/latest/contributor/install/index.html
Default, API is provided by apache2 wsgi.
But in my environment, this method can not successfully.
Another method, remove aodh apache2 wsgi, and create aodh-api service.
this method success.

How to use VersionPress to clone across servers?

I would like to clone a WordPress site that is already in VersionPress to a new server.
The instructions are generally only listed for cloning on the current server. I have one server dedicated to Dev and another for Production
I tried the following command line:
wp vp clone
--name=sitename
--ssh=username#site.school.edu
--path=/var/www/html/folder
--url=https://site.school.edu/destination
--dbname=mydb
--dbuser=myuser
--dbpass=mypass
--dbhost=xxx.xxx.xxx.xxx
--dbprefix=wp-
--force
However after I login to the remote ssh server, I get this error:
Fatal error: Call to undefined function apply_filters() in /var/www/html/atwiki/wp-includes/load.php on line 317
Error: Cannot connect over SSH using provided configuration.
Any ideas?
Here's a blog post on how to achieve that today. We will have a more polished way in the future.

Symfony2 run bin/vendors git error

I downloaded the latest symfony2 (2.0.10) and tried to run bin/vendors install but it prints the following:
Installing/Updating symfony
Cloning into /Users/i/sf2_proj/vendor/symfony...
error: Failed connect to github.com:80; Operation timed out while accessing http://github.com/symfony/symfony.git/info/refs
fatal: HTTP request failed
try using git:// instead of http:// in your deps file
Changing http:// to https:// also works

Resources