We are having difficulty trying to configure the gateway. I can make it work normally locally, similar to the documentation you provided, but as soon as I need to change the localhost addresses, everything starts to break down.
Our first endpoint runs on a Windows service (external service), our other endpoint runs on Azure Service Fabric, in particular, Stateless, which runs the web API. We get access to the service through a remote proxy server, which is necessary for communication with the service within the service network from the external structure of the service. This works great, as I can access my controllers and actions through the API through the reverse proxy port, but I continue to receive 504 Gateway Timeouts for the Gateway channel.
In my external service, I define a site with an address
http://clustername.azure.com:19008/MyApp/MyApiService/FCS.Fueling/
In my Azure Service Fabric Web API with no status, the channel is configured with an address
http://clustername.azure.com:8424/MyApp/MyApiService/FCS.Fueling/
19008 is the reverse proxy port. If I go to http://clustername.azure.com:19008/MyApp/MyApiService/api/values the
values are returned and the service is working fine.
8424 is the API port inside the service fabric. I also tried 19008 for the inbound channel, but to no avail.
FCS.Fueling is only the endpoint of the channel that I indicated. In localhost, both endpoints http: // localhost: 25000 / FCS.Fueling worked, messages were successfully received between my service and the external service.
I tried all kinds of combinations of localhost, removing the FCS.Fueling bit, different ports I get 504 Gateway timeouts.