IIS : Web application works inside IIS Server (Localhost) but not outside
IIS : Web application works inside IIS Server (Localhost) but not outside
I am experiencing problem with my web application which is configured on Port 90. It works fine if accessed within IIS Server i.e. right-click --> browse
but when I accessing it from outside, nothing happens.
I tried using IP address instead of server name.
I have configured application under root IIS (not under default website).
Applicatio name is: Myweb
default page: login.aspx
When I browse it locally , the link is: http:\\localhost\login.aspx instead of http:\\localhost\Myweb\login.aspx.
Except port I haven't configured anything else.
Could you please help?
Note: Server is discover able from outside, permissions are correct, application pools are correct.
I am experiencing problem with my web application which is configured on Port 90. It works fine if accessed within IIS Server i.e. right-click --> browse
but when I accessing it from outside, nothing happens.
I tried using IP address instead of server name.
I have configured application under root IIS (not under default website).
Applicatio name is: Myweb
default page: login.aspx
When I browse it locally , the link is: http:\\localhost\login.aspx instead of http:\\localhost\Myweb\login.aspx.
Except port I haven't configured anything else.
Could you please help?
Note: Server is discover able from outside, permissions are correct, application pools are correct.
Fethi ABASSI
Are You open port 90 through your windows firewall ?
If it's on port 90, you should need to specify the port in the URL (in addition to making appropriate firewall settings, as Fethi mentioned above).
Unless you explicitly specify a port in the URL, web browsers will always try port 80 for "http://..." and port 443 for "https://...".
Locally, your URL should be http://localhost:90/login.aspx and externally http://your.ip.address:90/login.aspx
Unless you explicitly specify a port in the URL, web browsers will always try port 80 for "http://..." and port 443 for "https://...".
Locally, your URL should be http://localhost:90/login.aspx and externally http://your.ip.address:90/login.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Apologies
the link is: http:\\localhost:90\login.aspx, which works fine internally (inside IIS) but doesn't work from outside IIS. I specified Server Name and Ip address also, as under
http:\\IIServerIPAddress:90\login.aspx
http:\\IIServerName:90\login.aspx
The reason I am haven't configured on IIS - Default website (Port 80) as the application Host.config seems got corrupt after I changed Administrator Password. ideally it should have been taken the new password and update the system configuration setting automatically, but not sure what went wrong and unable to determine at the moment
Please see a screenshot if I try to access an application configured under Default Website
Any help / suggestions are much appreciated
Thanks
IISError.JPG
the link is: http:\\localhost:90\login.aspx, which works fine internally (inside IIS) but doesn't work from outside IIS. I specified Server Name and Ip address also, as under
http:\\IIServerIPAddress:90\login.aspx
http:\\IIServerName:90\login.aspx
The reason I am haven't configured on IIS - Default website (Port 80) as the application Host.config seems got corrupt after I changed Administrator Password. ideally it should have been taken the new password and update the system configuration setting automatically, but not sure what went wrong and unable to determine at the moment
Please see a screenshot if I try to access an application configured under Default Website
Any help / suggestions are much appreciated
Thanks
IISError.JPG
IIS Web Core? When you use the IIS Web Core component, you are bypassing the Windows Process Activation Service (WAS).
Was it your intention to build an application that uses the IIS Web Core component instead of using IIS?
BTW: your application is running HTTP over port 900, not 90.
When using IIS Web Core, you are responsible for manually building the application.config file and declaring each aspect of what your application requires. Below is a reference to how to setup a config file when using IIS Web Code.
Link: https://msdn.microsoft.com/en-us/library/ms689327(v=vs.90).aspx
Dan
Was it your intention to build an application that uses the IIS Web Core component instead of using IIS?
BTW: your application is running HTTP over port 900, not 90.
When using IIS Web Core, you are responsible for manually building the application.config file and declaring each aspect of what your application requires. Below is a reference to how to setup a config file when using IIS Web Code.
Link: https://msdn.microsoft.com/en-us/library/ms689327(v=vs.90).aspx
Dan
Another link that explains that you, as the developer, will have to implement all of the necessary components in your app, if you decide to deploy your application in this configuration.
Link: https://blogs.msdn.microsoft.com/carlosag/2008/04/14/host-your-own-web-server-in-your-application-using-iis-7-0-hostable-web-core/
Take note of the last paragraph in the article.
Dan
Link: https://blogs.msdn.microsoft.com/carlosag/2008/04/14/host-your-own-web-server-in-your-application-using-iis-7-0-hostable-web-core/
Take note of the last paragraph in the article.
Dan
ASKER
The screenshot I have put is for another application where it seems applicationHost seems got corrupted and I am receiving this error since the password for Identity (Custom account) is changed
So I would change the account password back to whatever it was and see if it resolves your issue.
Dan
Dan
ASKER
Thanks Dan. I had to open Port 90 both Inbound and Outbound on IIS Server