When I run query.js (similar to query.js in fabcar but modified for my application), I keep getting an error which says,
Failed to connect before the deadline
I have changed the localhost to docker IP address in enrollAdmin.js and registerUser.js
TLS is enabled for peer, orderer and cli.
Any help would be appreciated. Thanks
I had the exact same problem. These steps fixed it for me:
Open VirtualBox Manager and select the “default” VM
Click “Settings”, “Network”, “Advanced”, “Port Forwarding”.
Create a new rule by clicking the “+” sign on the right and entering the following: Name -> “grpc”, Host Port -> 7051, Guest Port -> 7051
You can leave the Host IP and Guest IP unspecified.
Thx to: https://developer.ibm.com/opentech/2017/11/29/running-hyperledger-fabric-windows-revised/
I had the same problem:
I think grpc and fabric-client package has issues or different versions than we need (verify the package.json for npm) . Therefore I decided to manually install the latest versions of the npm fabric-ca-client, fabric-client and grpc packages and it worked!!!!
I hope this solution works for you!!
I had the same issue as well
What works for me is that I reinstall the global window-build-tools and global grpc, and it works afterwards. Hope it helps!
What worked for me was changing the localhost to Docker's IP(seen when the docker terminal starts) in the network connections file(either connections.json or networkConnections.yaml) being used in the query.js(or any other js).
Related
I'm trying to set up a new JFrog Artifactoy OSS server on a Windows 10 machine.
While it actually seems to be up and running the UI is not working. When trying to open http://localhost:8082/ui/ I just get a "Service unavailable" error.
In the /var/log/frontend-service.log I see the following error:
[main ] - Couldn't register on Router, retry number: 120, Error : [Trying to connect an http1.x server]
I couldn't find any errors in the other logs.
I already made some desperate attempts in my system.yaml like setting the IP manually, tested setting a proxy, etc. But no luck. Any ideas what might be going on here?
I also had the same problem, I solved it by exposing port 8082 as well:
docker run --name artifactory -d -p 8081:8081 -p 8082:8082 docker.bintray.io/jfrog/artifactory-oss:latest
I had this issue with version 7.7.3 and I just reverted to an older version I had 7.5.7 and it worked fine for me.
I try to install ForestAdmin but get an error after set up my account and generate my lumber db.
What I did :
lumber generate -c 'mongodb+srv://ugo:<my-password>#tlf-qraep.mongodb.net/test?retryWrites=true&w=majority' test
cd test
npm install
npm install lumber-forestadmin --save
lumber install lumber-forestadmin --email <my-mail> --projectName test
npm start
I got this message so I clicked on it
Your admin panel is available here: https://app.forestadmin.com/49189
I re-entered my password but I got this error message :
"Unlock your data
Oops, cannot reach your application. Are you sure it is running? If your application is running, you might have a CORS configuration issue."
I checked and my server running on port localhost 3000.
Someone already got this error message?
Thx for the help guys.
I finally succeed to remove the error. I generated a new lumber on an other port (3003 rather than 3000) and it worked for me !
Maybe another app is using the 3000 port ?
I've successfully completed the ./install.sh command. When I run the next "~/mcdev start -o" I receive this error: "Starting Microclimate
Pulling microclimate-file-watcher (ibmcom/microclimate-file-watcher:1809)...
ERROR: Get https://registry-1.docker.io/v2/ibmcom/microclimate-file-watcher/manifests/1809: net/http: TLS handshake timeout
Error starting Microclimate"
I have running on my pc:
git version 2.17.1 (Apple Git-112); Docker version 18.06.1-ce; MacOS
High Sierra v 10.13.6; latest Microclimate v18.09
My network is up and I don't have any proxy.
What am I missing or doing wrong?
I got this to work by changing to a different wifi \ internet connection. Still not sure why my home wifi, with no restrictions that I'm aware of, will 'block' the dependency downloads upon start of Microclimate.
If anybody has additional info to help find the root cause please feel free to share.
This docker error generally shows up when your internet connection is too slow for Docker, as it times out performing the TLS handshake. This would also explain why moving to another network fixes the issue.
I'm trying to connect to an Azure file share from my Mac running High Sierra 10.13.6 using the following command:
mount_smbfs -d 0777 -f 0777 //dolphins:PASSWORDHERE#dolphins.file.core.windows.net/models /Users/b3020111/Azure
However I keep getting the error:
mount_smbfs: server connection failed: No route to host
I have turned off packet signing in /etc/nsmb.conf:
[default]
signing_required=no
After looking around the web I seem to be at a loss as to where to go, any help is appreciated.
I got it working with azure provided connection example.
mount_smbfs -d 777 -f 777 //user:key#storageurl/folder ~/mountfolder
Folder in file share needed after url and mountfolder must exist.
But the main reason for "No route to host" was because the access key had forward slash in it! I did a rebuild of key1 until I got a key without forward slash.
BUT! Be aware, rebuilding key will kill all mounts and connections to that storageaccount.
Came across this issue myself today. Do double check that your ISP does not block SMB port 445. In my case, AT&T does actually block this port. I found this in their guide http://about.att.com/sites/broadband/network
The solution for me was to connect with a VPN which I'm already hosting on Azure. Additionally as others have mentioned in this thread, escape any / with %2f. Also, add the share name in the connection URL. For example, if your share name is my-data then the connection URL should contain xxx.file.core.windows.net/my-data.
This is omitted for some reason in the Azure docs/UI and was required for successful connection on OSX.
It was the "/" after all. I had to regenerate the key over ten times till I get a key that doesn't have the "/" character and then it worked fine through the terminal.
It should work using the following syntax:
mount_smbfs //<storage-account-name>#<storage-account-name>.file.core.windows.net/<share-name> <desired-mount-point>
Without adding the permissions.
Via Finder:
Source can be found here
"mount(2) system call failed no route to host "
while mounting azure file share on linux vm we can have this error.
In my case One package was missing which is - cifs-utils
So, I have used below command
"sudo yum install cifs-utils -y" to resolv the issue.
Important to allow port 445 (TCP) to smb communication. If you don't access it, your firewall block it! Please enable it and try it again.
I ran into this same problem, and while I was never able to get it working through the terminal I did manage to get it resolved in finder.
Essentially the same instructions as #Adam Smith-MSFT, however one key difference.
I created a directory via Azure's web interface, and after that I was able to connect by adding /<directory-name> to the connection string. Without a directory this would not work at all.
I am struggling with the Bower's installation behind my company's network.
Despite of setting npm proxy and bower proxy (in the .bowerrc file), as suggested in many other posts, I still get this error:
bower ECONNREFUSED Request to https://bower.herokuapp.com/packages/bootstrap-sass-official failed: connect ECONNREFUSED
On the other hand node, npm and grunt seem to work well.
Can anybody help with some other idea about how to tackle the problem?
Try to create a file named ".bowerrc" inside your user profile (usually at "C:/Users/[YOUR USERNAME]" or "%USERPROFILE%" shortcut).
Try to put this inside your file and save:
{
"registry": "http://bower.herokuapp.com"
}
If that doesn't work, try to put this:
{
"registry": "http://bower.herokuapp.com",
"proxy": "http://<user>:<pwd>#proxy.host.br:8080",
"https-proxy": "http://<user>:<pwd>#proxy.host.br:8080",
"strict-ssl": false
}
PS.: You will need to know your company's proxy address.
Have you tried:
http_proxy='proxyserver' https_proxy='proxyserver' bower install
?
{
"directory": "library",
"registry": "http://bower.herokuapp.com",
"proxy":"http://<USERNAME>:<PASSWORD>#<PROXY_IP>:<PROXY_PORT>/",
"https-proxy":"http://<USERNAME>:<PASSWORD>#<PROXY_IP>:<PROXY_PORT>/"
}
This code worked for me. I am using Win 7 and chrome and also git bash. Here few things need to be cleared. This takes me huge time to find the actual data regarding the user name, password, proxy IP and Port. I will describe it step by step so that every learners can easily grasp the message:
Create a file in the notepad named .bowerrc in the login folder; You can go there by typing at Start>Run>%UserProfile% and press OK.
Type above code in the .bowerrc file with the following changes:
Replace <USERNAME> with your internet connection user ID or login ID
Replace <PASSWORD> with your internet connection password or login password.
Replace <PROXY_IP> and <PROXY_PORT> with the working proxy IP address and its port number.
Note: There should be no angle brackets.
Proxy IP should be different than your own IP.
Before using any proxy IP and port you should check it is working by changing your proxy IP and port.
You can go through this link to know the details of proxy settings at description here
From this proxy settings you will get Proxy IP and Port.
Recheck all the input so that all are correct and save and close the file.
Open git bash and change directory to the project file and type command and hit enter, in my case, git bash command:
a#a-PC MINGW32 /d/conFusion
$ bower install
It worked like magic.
In my case, my .bowerrc file was using a proxy (so .bowerrc had both proxy and https-proxy properties set, without any username or password).
Those were causing me the ECONNREFUSED.
https://github.com/jquery/jquery.git", exit code of #128 fatal: unable to access 'https://github.com/jquery/jquery.git/':
Failed to connect to webproxy.wlb2.nam.nsroot.net port 8080: Connection refused
Additional error details:
fatal: unable to access 'https://github.com/jquery/jquery.git/':
Failed to connect to webproxy.wlb2.nam.nsroot.net port 8080: Connection refused
I removed them, (my current internet connection is not behind a proxy), and so errors stopped.