Setting the base url does not determine what URL the Jira site is actually listening on. It only tells the application what URL is expected to be used to serve up the content.
Since you can reach the site on the localhost address, that is at least a good sign that JIra is up and working. The problem most likely lies with the configuration of the reverse proxy itself. If you followed all the steps in that guide though https://confluence.atlassian.com/adminjiraserver071/integrating-jira-applications-with-iis-802593039.html then you should have had to setup another connector for Jira's server.xml file using a different port (usually something other than port 8080).
Is the IIS on a separate server from Jira or the same server? Basically I would also want to make sure there are no ports being blocked between these two servers. Windows is known to have a firewall that blocks all external traffic from reaching servers until you either create a port forwarding rule or disable the software firewall for that machine.
It might help to start from either the Jira server or the IIS instance and first make sure that you can ping each machine from the other. If you can't ping them, then clearly there is a problem with getting this traffic between the two instances. In which case, I would say the next steps are to identify what addresses are in use for each machine. It's possible each machine has multiple network interfaces. On windows you can find all of these in the command prompt with a command such as "ipconfig /all".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.