We are trying to access the api gateway that is on a mobile server externally, we can confirm it works locally by running curl --insecure --request GET “https://mobile-6/api/.well-known/uris”.
It tells me that it is the external routing that isn’t working not the AP Gateway setup. This is not my area of expertise as an expert only on the APIs, sorry.
As far as I’m aware the mobile server service does not have an /api/.well-known/uris endpoint. The API Gateway is unrelated to the mobile server - it actually runs within IIS on your Management Server with its own virtual path and application pool. I’m guessing the mobile server (which listens on port 8081 for http or 8082 for https by default) is installed on “mobile-6” along with the management server, and the reason the request works locally is because you’re hitting IIS instead of the mobile server. But externally I wonder if that video6 URI is proxied to port 8081/8082 where that endpoint doesn’t exist?
Thank you for your response. Any chance you would know a bit on how the external routing is supposed to look? We’ve made some changes and configured the mobile server for webclient access. But still no luck.
The API gateway and the Mobile Server service are two different services available on different ports. They can, and often do, live on different servers but might be on the same server in your environment.
The /api/.well-known/uris endpoint is on the API gateway and is only available on the Management Server on port 80/443 (by default). The Mobile Server APIs are different, and available on port 8081/8082 (by default).
