Forum Widgets
Latest Discussions
UPDATE: IIS no longer serving up one of my websites
I have two websites on my windows 10 desktop: http://www.gregsnativelandscapes.com.au: This one is working fine. https://www.gjb.au This one is not working - all I get is This site can’t be reached The connection was reset. What the hell? I have checked: The bindings - https, correct domain name Both web sites are started. I have done ISSRESET. Checked my A records in Webcentral account. I have gone through the IIS settings of each website and checked that they are all the same - they are. So what else do I need to check? Is there a specific IIS troubleshooter available that I can download and run?gregarybMay 12, 2026Copper Contributor13Views0likes0CommentsIIS on Windows 10 no longer serving my websites
My websites were working, i.e. I could access them on my mobile phone. But something has happened abd they are not longer accessible - "NOT FOUND" I have checked: The bindings - https, correct domain name Both web sites are started. I have done ISSRESET. Checked my A records in Webcentral account. So what else do I need to check? Is there a specific IIS troubleshooter available that I can download and run?gregarybMay 06, 2026Copper Contributor16Views0likes0CommentsIIS setup a web site to be accessed without a domain name....how?
I want to setup a web site for testing without a domain name. I have 3 web sites with domain name that are working fine. I am working on a web site for Millhouse and they already have an existing web site with the domain name millhouse.org.au I want to setup their new web site on my web server for testing purposes and so member of the organisation can view it (as http) to assess it. I want to be able access it like this: 58.168.225.214:8080 But what I have done so far isn't working: I have setup port fording in my modem with WAN and LAN ports of 8080. And 8080 as the port in the web site settings in IIS.GregaryJan 08, 2026Copper Contributor83Views0likes0CommentsIIS Site Randomly Returns 404 While App Pool Remains Started
Hello, We have an IIS site running behind Azure Front Door that becomes unavailable every few days. Symptoms: Application Pool remains started Users see the blue "Not Found" page from Azure Front Door When accessing the site directly on the server during the failure, we get a 404 from IIS, not Front Door The site does not recover on its own Recovery requires an App Pool recycle or IIS restart, and sometimes a full server reboot because recycle or IIS restart does not help What it is NOT: No CPU, memory, disk, or network pressure Event logs do not correlate with the outage When it happens: Random and unpredictable Any insights would be appreciated. From the server itself: Please your support.captainitDec 26, 2025Copper Contributor103Views0likes0CommentsHTTPS Reverse Proxy on IIS 10 – External Access Fails (Timeout) Although Local Requests Work
Hello everyone, I’m currently facing an issue with an IIS 10 reverse proxy configuration on Windows Server, and I would really appreciate your guidance. Environment Windows Server IIS 10 Application Request Routing (ARR) + URL Rewrite enabled Backend application running on: http://localhost:8080/ http://localhost:8080/login Public domain: https://lojistik.abc.com.tr What I want to achieve I want users to access the backend web application through the following URL: https://lojistik.abc.com.tr/LMYS/login Internally, IIS should proxy this to: http://localhost:8080/login What works The backend application is accessible without issues: http://localhost:8080/login From the server itself, reverse proxy works: Invoke-WebRequest "https://lojistik.abc.com.tr/LMYS/login" → StatusCode: 200 (success) What does NOT work From any client machine, the following request results in a timeout: https://lojistik.abc.com.tr/LMYS/login Browser shows connection timeout. No entry appears in IIS logs for external requests to /LMYS/.... Tests performed ▪ netstat -ano | findstr :443 on the server → Port 443 is listening ▪ DNS resolves correctly: lojistik.abc.com.tr → 10.6.130.90 ▪ Reverse proxy rule on IIS is correctly configured under the HTTPS binding site: Pattern: ^LMYS(/.*)?$ Rewrite to: http://localhost:8080{R:1} ▪ ARR Server Proxy is enabled. Key observation Requests from the server itself succeed (reverse proxy returns 200), but external clients always time out, which suggests that the HTTPS traffic is not reaching IIS at all (likely blocked or not NAT-forwarded on the network path). Question What could cause HTTPS (port 443) traffic to reach IIS locally, but external requests to the same port to hang indefinitely? Any guidance would be greatly appreciated. Thank you in advance. Best regards,raysefoNov 22, 2025Copper Contributor177Views0likes0CommentsIIS app pool in-memory cache miss
Hi, Our IIS server runs on windows 2016 servers, recently we are experiencing frequent miss from in-memory cache, and instead of connecting to NCache which is our cache solution, it is sending request to database. After lots of debug we still could not identify the issue here. But as a best practice we are going to change some setting. But, one suggestion is to change max worker count from 4 to 1. Will that impact our performance? How much will it be effective to bring that value to 1 from 4, in terms of single worker cache miss issue occurrences?indrajitOct 21, 2025Copper Contributor164Views0likes1CommentBinding a website that already uses required port.
Hello devs, I hope you are having a great day. I have already developed a website that runs on port 8081 in localhost. When i start a new site in IIS and set 8081 as the port in the bind section(which is already open via the website), I receive the error that the port is already in use. My question is how can I connect my domain to the local host and specified port in IIS or any other application. The IIS has a default website(which brings the welcome page up) and by using that the connection between domain and server is assured(name servers are set and ready). If only the IIS could relay all traffic to the localhost and port 8081 of the server, my problem would be solved. I have attached some pictures for better understanding. Thank you in advance Best wishes, Sahand -As you see in this picture my website has started and working in the specified IP and port. ,-In this picture while binding the new website to port 8081 the IIS refuses to start the site with this error(port 8081 is already in use by my website).IIS App pool crashes
Hi, We are experiencing some random app pool crashes on one of our production servers. I've put in place additional logging and analysed it through DebugDiag. The output from that is: In w3wp.exe.11696.dmp the assembly instruction at clr!Assembly::GetSecurityDescriptor+1a in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000040 on thread 9 I need further help to troubleshoot this and this seemed like the best place, but if it's not I'd appreciate someone pointing me in the right direction. Happy to post the full report if that would help or any other information that would be of use. Thanks.nealcaxiellAug 07, 2025Copper Contributor539Views1like1CommentIIS SERVER_PROTOCOL never returns HTTP2 (HTTP/2)
Using Windows Server 2025, I can not get the "SERVER_PROTOCOL" response header to return anything other than HTTP/1.1: For example, a simple classic ASP page with: <% Response.Write(Request.ServerVariables("SERVER_PROTOCOL")) %> Always returns "HTTP/1.1". I have verified the page is served via HTTP2 via developer tools in the browser and it's even upgraded to HTTP3/QUIC later on in the response sucessfully.DJXJul 07, 2025Copper Contributor353Views0likes0Comments
Tags
- IIS25 Topics
- https5 Topics
- http4 Topics
- url rewrite3 Topics
- IIS Windows Server 20223 Topics
- url authorization rules2 Topics
- roadmap2 Topics
- exchange2 Topics
- windows server2 Topics
- bindings1 Topic