Our chirpstack API (gRPC) connection works fine when testing on a local machine, but as soon as we move the image to an Azure App Service it doesn't work anymore. The logs are full of different errors, but I think this is the main one: debug_error_string = "{"created":"@1663776130.896090920","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3260,"referenced_errors":[{"created":"@1663776130.896090212","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":167,"grpc_status":14}]}"
It seems that from within the gRPC host is unreachable or it can't respond properly. Is the Azure App Service using some kind of proxy which prevents this scenario? At the moment our Python code within the container is exposed via HTTP on port 80. I toggled HTTP 2.0 Proxy in Azure App Service, but it doesn't seem to change anything. The setting HTTPS Only (redirects) is also turned on.