{"id":1259,"hash":"1b672bccef5cbb8c1507e8d9647c3c5c2fc4459b90c3750ff11c9ec4d75a12c7","pattern":"GRPC - nodejs DNS resolution failed","full_message":"I'm working with a GRPC service hosted with HTTPS and self-signed cert. When I connect using syntax like:\n\nconst client = new productService('https://grpc-server-xxx.com:9090',\ngrpc.credentials.createInsecure())\n\nI am getting the error like this\n\n{ Error: 14 UNAVAILABLE: DNS resolution failed\nat Object.exports.createStatusError (C:\\grpc\\node_modules\\grpc\\src\\common.js:91:15)\nat Object.onReceiveStatus (C:\\grpc\\node_modules\\grpc\\src\\client_interceptors.js:1209:28)\nat InterceptingListener._callNext (C:\\grpc\\node_modules\\grpc\\src\\client_interceptors.js:568:42)\nat InterceptingListener.onReceiveStatus (C:\\grpc\\node_modules\\grpc\\src\\client_interceptors.js:618:8) at callback (C:\\grpc\\node_modules\\grpc\\src\\client_interceptors.js:847:24)code: 14,metadata: Metadata { _internal_repr: {}, flags: 0 },details: 'DNS resolution failed'\n\nAnyone help me how can I resolve the issue.\n\nNote: \nMy OS is Windows 10,\nnodejs -- v10.16.0,\nGRPC","ecosystem":"go","package_name":"node.js","package_version":null,"solution":"The gRPC library does not recognize the https:// scheme for addresses, so that target name will cause it to try to resolve the wrong name. You should instead use grpc-server-xxx.com:9090 or dns:grpc-server-xxx.com:9090 or dns:///grpc-server-xxx.com:9090. More detailed information about how gRPC interprets channel target names can be found in this documentation page.","confidence":0.95,"source":"stackoverflow","source_url":"https://stackoverflow.com/questions/62108070/grpc-nodejs-dns-resolution-failed","votes":6,"created_at":"2026-04-19T04:52:44.560551+00:00","updated_at":"2026-04-19T04:52:44.560551+00:00"}