So I am trying to build a test environment on the same subnet as an RPC over HTTPS server.
- The certificate works fine I have validated that the new web works externally For example, my test site is called https://support.m-files.com/supportportal/article-details/url?recordId=Firewall-Settings-Ports-Needed. This is all good and well, it works on my legacy server, but as I said, I'm trying to get gRPC working with the new web and also integrate it into Azure.
My first is issues are that my new test enviroment is conflicting with my legacy old enviroment, so in short i want to customize all the ports in the test enviroment so i can do my networking rules etc, to just run on other ports so i dont have conflicting servers, which was what was happening before.
So right now all I have up and running is the installation, I have had to disable all my routing for now until I understand what I'm missing.
My Firewall is completely disabled for testing from the server to itself. So the client is installed on the server.
If I do a test connection, I get this on gRPC
PropertyPageVault.cpp, 663, Network problems are preventing M-Files from communicating with the server. (0x800400ED)
Helper.cpp, 380, Network problems are preventing M-Files from communicating with the server. (0x800400ED)
GrpcSession.cpp, 83, Network problems are preventing M-Files from communicating with the server. (0x800400ED)
GrpcHandle.cpp, 97, Network problems are preventing M-Files from communicating with the server. (0x800400ED)
GrpcHandle.cpp, 97, gRPC connection to the server failed. (0x80040159)
(M-Files 25.5.14829.4 2025-06-30T13:14:04.116Z)
If I use the IP it's fine.
If my external firewall rules are in place, it work,s but then my legacy server stops working, even though they have different DNS names different DNS servers and IP's
Summary
-
Your cert is now correctly trusted
-
TLS 1.2 with
ECDHE-RSA-AES256-GCM-SHA384is in use -
The 400 error is purely from not sending proper HTTP content
-
You can now build on this with mutual TLS, API testing, or full HTTPS app validation
What is strange is I can't even get the client that's installed on the server to connect via gRPC, Should I be fiddling with an DNS records on the DC? Like PTR records or reverse lookups?
Once I get the client to work, I can make progress from there. I got the web to work, so that's fine. Once the client and web works I'll need to look at configuring Trafik and dockker.
I have no Proxy server set up as of yet.
Thank you
Any suggestions?
