James Newton-King
James Newton-King
I'm not sure what could cause that error. This is the difference in changes that happened between 3.0.14 and 3.0.15: https://github.com/JamesNK/Newtonsoft.Json.Schema/compare/3.0.14...3.0.15 There were no changes to the `License` or `LicenseHelpers`...
I don't know why you're seeing a RST_STREAM. If a request sends a response message, even an empty one, then the response should end with a HEADERS frame with END_STREAM...
@rzikm Is there a way to make the error message clearer in the client so people can self-diagnose this issue?
Hosting gRPC on IIS - Trailers are not supported for this response. The server may not support gRPC.
Windows 10 isn't supported. IIS requires Windows 11/Windows Server 2022 or greater. See https://learn.microsoft.com/en-us/aspnet/core/grpc/supported-platforms?view=aspnetcore-7.0#supported-aspnet-core-servers
Hosting gRPC on IIS - Trailers are not supported for this response. The server may not support gRPC.
The error does say "The server may not support gRPC."
Unfortunately the client error doesn't provide much information. What do the server logs say?
It looks like this is the important bit: > Container fmsynclinuxqa_0_4d5f8a95 didn't respond to HTTP pings on port: 8080, failing site start. For some reason, your website isn't responding to...
I believe so. I haven't heard of other documentation. cc @jeffwmartinez
@jeffwmartinez A lot of places link to https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/gRPC/use_gRPC_with_dotnet.md. Could it be updated to point to fixed documentation?
From now on, please discuss gRPC + Azure issues in Azure forums. Those are the best places to get help related to Azure.