Hi,
We are running M-Files 26.1.15632.8 in a multi-server load balanced environment with two M-Files servers. Randomly, the Web Client on one server stops working while:
Desktop Client continues working normally
REST API continues working normally
/health endpoint still returns TRUE
Restarting M-Files Server service fixes it temporarily
Through investigation we found that the Web Client initialization requests (resolve-maturity-of-feature, query-version, get-server-capabilities) return 502 Bad Gateway from IIS, pointing to /grpc/v1/ endpoints. The mf-grpc-web-server.exe (Node.js) process is running and responding on port 7767, but IIS cannot proxy to it successfully.
Has anyone experienced similar issues? Specifically:
gRPC web server returning 502 while still running
Any known issues with mf-grpc-web-server in multi-server setups
Whether restarting only a specific service resolves it without full MFServer restart
Thanks
