After deploying my server on Cloud Run, calling the endpoint with BloomRPC or other clients, the service returns "error": "2 UNKNOWN: No status received". Calling the server locally with PORT=7000 node index.js on localhost:7000 works fine. I guess Cloud Run is adding some TLS magic somewhere and maybe resets the headers but I have no idea how to fix that.
Here's my code:
const grpc = require("@grpc/grpc-js");
const protoLoader = require('@grpc/proto-loader');
const reportGenProto = protoLoader.loadSync("reportGen.proto");
const packageObject = grpc.loadPackageDefinition(reportGenProto);
const server = new grpc.Server();
server.addService(packageObject.ReportGeneratorService.service, {
Ping: async function (call, callback) {
console.log("PONG");
callback(null, {
pong: "pong"
});
},
});
server.bindAsync(`0.0.0.0:${process.env.PORT}`, grpc.ServerCredentials.createInsecure(), (err) => {
if (err) throw err;
console.log('Server running on port', process.env.PORT);
server.start();
});
And this is the .proto:
syntax = "proto3";
service ReportGeneratorService {
rpc Ping (Empty) returns (Pong) {}
}
message Pong {
string pong = 1;
}
message Empty {}
Cloud Run logs don't say anything other than that console.log("PONG"). I've tried enabling HTTP/2 even though I'm not using streams but the same thing is returned.
I'm building and deploying inside a Docker container, as I need some dependencies for what I'll do later with the server. This is the Dockerfile:
# we just need the LibreOffice environment to convert the file, this we'll do
FROM ideolys/carbone-env-docker
ENV DIR /app
WORKDIR ${DIR}
COPY . ${DIR}
RUN npm install
ENV TZ Europe/Rome
CMD [ "node", "index.js" ]
I'm also adding that using the deprecated gRPC node package works fine without changing anything in the configuration. The problem happens only when using the new grpc-js package.
