Hey everyone! I'm dealing with a bit of an issue related to IIS while working with an internal app called RS2, which has a Swagger API built-in. I've never really needed to use IIS before, but recently we decided to integrate an external service with RS2, which required me to set up IIS on our 2019 server VM.
I went through the whole process: installed IIS, got a SSL certificate, and created a site entry under the default website for the fully qualified domain name (FQDN) on a specific custom port.
The Swagger API works perfectly when I access it via local IP and the port, but when I try to reach it with the FQDN and the specified port, I just get the default IIS welcome page instead of the Swagger API. It feels like there's something I missed that's causing this issue. Any ideas on what could be preventing the API from responding to the FQDN?
1 Answer
It sounds like you might need to check the site bindings in IIS. Make sure the default site is not enabled if you're using your custom site. You can bind multiple sites to the same port using a domain name, so that might be the problem.
Just to add on: even when I hit the URL with the IP and port, https://IP:port/swagger takes me to the API, but hitting https://fqdn:port/swagger gives me a 404. Under 'Sites' in IIS, it looks like I only have the default site active.