Error : 14 UNAVAILABLE: DNS resolution failed on BloomRPC golang GRPC - go

I'm figuring out how I can test my golang project using Bloomrpc. I've turned on the backend server, client server and db server but an error pop up like this on Bloomrpc:

Related

Issue connecting my lambda function to Amazon managed blockchain

I am failing with a DNS 14 message when trying to call a lambda function to invoke chaincode on my Amazon Managed Hyperledger Blockchain.
ERROR Failed proposal response. Status code: undefined. Message: 14 UNAVAILABLE: DNS resolution failed. Stack: Error: 14 UNAVAILABLE: DNS resolution failed
at Object.exports.createStatusError (/opt/nodejs/node_modules/grpc/src/common.js:91:15)
at Object.onReceiveStatus (/opt/nodejs/node_modules/grpc/src/client_interceptors.js:1209:28)
at InterceptingListener._callNext (/opt/nodejs/node_modules/grpc/src/client_interceptors.js:568:42)
I believe that it is due to a grpc link used to access the peer node endpoint.
I've tried logging all of the request fields, but it is difficult to figure out which configuration is missing.
Try to perform nslookup against the peer address. If it fails, see whether you have created VPC Endpoint for the Hyperledger Fabric network.

Laravel WebSockets - deployment - fails to connect the websocket

I am trying to deploy my laravel project with websockets built on Beyond Code's package.
My server is on AWS and i'm using WHM.
on the cPanel's terminal i'm running the line php artisan websockets:serve
and i get the result Starting the WebSocket server on port 6001...
when i'm loading the page with the websocket's connection sometimes i get the error failed: Error during WebSocket handshake: Unexpected response code: 200
and sometimes i get the error failed: WebSocket is closed before the connection is established.
On AWS EC2's Security Groups i allowed the Custom TCP port 6001 and 6002
Any suggestions to fix it?
Maybe a good deployment tutorial for Laravel WebSockets?
I'm looking for answers all over the internet and i get nothing useful.

wstransport.js:218 WebSocket connection to 'wss://chunderw-vpc-gll.twilio.com/signal' failed: Unknown reason

I'm getting this error while integrating Twilio task router. on localhost, so I thought might be its https error so I tried through Heroku but still getting the same error.

Google Cloud Endpoints Sample for Go using gRPC response service fail

I am new using cloud platform. I trying to deploy a service using go and grpc. I found this tutorial https://github.com/GoogleCloudPlatform/golang-samples/tree/master/endpoints/getting-started-grpc and everything was complete successful until I have to call the service.
In the moment that I use the client to call the service I get this error:
could not greet: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 35.199.74.154:80: connectex: 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.
I would like to know if someone can help me with that problem.

Javascript Adapter throwing java.net.SocketException: Connection reset

I am trying to make a https call to the backend server that gives a json data , i could get the by making https calls using browser but when make the same call using the javascript adapter i getting this output
I followed this IBM Knowledge Center to add the cert to the default mobilefirst keystore. I am not sure why i am getting this error?
[ERROR ] FWLSE0099E: An error occurred while invoking procedure [project kmf]login/HttpRequestFWLSE0100E: parameters: [project kmf]
Http request failed: java.net.SocketException: Connection reset
FWLSE0101E: Caused by: [project kmf]java.net.SocketException: Connection resetjava.lang.RuntimeException: Http request failed: java.net.SocketException: Connection reset
at com.worklight.adapters.http.HTTPConnectionManager.execute(HTTPConnectionManager.java:271)
at com.worklight.adapters.http.HttpClientContext.doExecute(HttpClientContext.java:201)
at com.worklight.adapters.http.HttpClientContext.execute(HttpClientContext.java:185
From the comments, by Vivin:
Connection reset means , the backend server has reset the connection. You should consult your network team/ backend team and verify why this occuring. Firewalls / network issues / backend server connection issues are all possibilities. MobileFirst server is only reporting the issue as it found

Resources