Solution:
sudo vim /etc/resolv.conf
Just restart the network
Read More:
- [Solved] Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050
- [Solved] Fabric 2.x: error starting container: API error (404): network_test not found
- CDH-hue : Could not start SASL: Error in sasl_client_start (-4) SASL(-4): no mechanism available
- Kubernetes Error: Error in configuration: unable to read client-cert* unable to read client-key*
- [Solved] Use the truss console to connect to the public blockchain network error: mnemonic invalid or undefined
- [Solved] Chrome Error: The request client is not a secure context
- Gitlab nginx wont start to work. [down: nginx: 1s, normally up, want up; run: log: (pid 20128)xxx]
- How to Solve Client-go Mod Error
- Nginx Container Error: nginx: [emerg] mkdir() “/var/cache/nginx/client_temp“ failed (13: Permission denied)
- [Solved] jedis Connect redis Error: connect timed out
- [Solved] Failed to connect to server(code:1006)
- [Solved] Error: Could not open client transport with JDBC Uri
- How to Solve creating bean with name ‘mappingjackson2httpmessageconverter’ error when elasticsearch advanced client starts‘
- Failed to connect to driver at XXXXXXx
- [Solved] ClientError.Security.Unauthorized: The client is unauthorized due to authentication failure.
- [Solved] dyld: Library not loaded: /System/Library/Frameworks/Network.framework/Network
- Robo3T Remote Connect MongoDB Error: Failed to refresh ‘Collections‘. Error: ListCollections failed
- [Solved] Nginx Request 500 Error: CreateFile() “/temp/client_body_temp/0000000013” failed (5: Access is denied)
- How to Solve Error: could not read ok from ADB Server.failed to start daemon error: cannot connect to daemon
- How to Solve bootstrap.sh error during the construction of fabric environment