I get errors while building your first network
I was able to run this command ./byfn.sh generate and can see peers and orderer generated.
With the command ./byfn.sh up I get the following error:
ERROR: SSL error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661) ERROR !!!! Unable to start network.
Related
I'm following the official installation instructions.
When I run the last command, bash vst-install.sh, I get the following error:
Retrieving http://rpms.remirepo.net/enterprise/remi-release-.rpm
curl: (22) The requested URL returned error: 404
error: skipping http://rpms.remirepo.net/enterprise/remi-release-.rpm - transfer failed
Error: Can't install REMI repository
I see that the url that the script is trying to curl, is missing a release number towards the end after remi-release-.
Why is this happening and what could I do?
file_get_contents(): SSL operation failed with code 1. OpenSSL Error
messages: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Getting this error in local server. Working fine in Production
OS: macOS Mojave
Hi I am trying to run developer tutorial on hyperledger-composer from https://hyperledger.github.io/composer/latest/tutorials/developer-tutorial.html
I have setup the development environment successfully.
I receive the following error
Error trying to start business network. Error: Unable to initalize
channel. Attempted to contact 1 Peers. Last error was Error: Error: 14
UNAVAILABLE: Trying to connect an http1.x server
while I run the following command
composer network start --networkName tutorial-network --networkVersion
0.0.1 --networkAdmin admin --networkAdminEnrollSecret adminpw --card
PeerAdmin#hlfv1 --file networkadmin.card
I have checked the fabric is running and is listening to business network archive
"Listing Business Network Archive from tutorial-network#0.0.1.bna
Identifier:tutorial-network#0.0.1
Name:tutorial-network
Version:0.0.1
Command succeeded"
P.S I am behind firewall/proxy
Configuration
Node #8.11.3
composer #0.19
Mac OS High Sierra
I installed DockerToolbox-1.11.2 on Mac ElCapitan. When i try to run the "Docker Quickstart Terminal" i get an error as below
Running pre-create checks... (default) Unable to get the latest
Boot2Docker ISO release version: Get
https://api.github.com/repos/boot2docker/boot2docker/releases/latest:
x509: certificate signed by unknown authority Creating machine...
(default) Unable to get the latest Boot2Docker ISO release version:
Get
https://api.github.com/repos/boot2docker/boot2docker/releases/latest:
x509: certificate signed by unknown authority.
But it seem to have created the VM.
When i run any docker command it ends up with a timeout error.
An error occurred trying to connect: Get
https://192.168.99.100:2376/v1.23/containers/json: Gateway Timeout
But when i try to run "docker run" on docker-machine it gives the same error as the initial one.
docker#default:~$ docker run hello-world
Unable to find image'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
docker: Error while pulling image: Get
https://index.docker.io/v1/repositories/library/hello-world/images:
x509: certificate signed by unknown authority.
See 'docker run --help'.
I guess the issue is related to proxy certificates, tried searching for a solution to this issue but have not found any yet.
Will appreciate any help regarding this.
I'm having problems installing composer. The error being displayed is:
Connection Error [ERR_CONNECTION]: Unable to connect to getcomposer.org
Proxy http####://10.50.7.154:3128### [from Internet Settings] failed with errors:
Failed to open stream: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Request to https://getcomposer.org/installer failed with errors:
Failed to open stream: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
That's a proxy problem, right there. Please step away from the building you are in and find a regular coffeeshop with regular broadband WiFi.
Hope this helps.