-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug with manage.iis.net's interface #25
Comments
What browser was this running in? Is there an error being displayed in the developer console (F12)? |
I also only see the default site in both IE11 and Chrome. In the Console for Chrome I get: Uncaught SyntaxError: Unexpected end of JSON input(anonymous function) @ content.js:7 |
Done. Same error in Chrome. FWIW I get no console errors in IE but still only see the default site. When I go to App Pools I see the entire list. [cid:[email protected]] Can you try clearing the cache and reloading? The easiest way is to check the "Disable cache" box as shown in the picture. — |
I'm not by my workstation ATM. But I was using Firefox when I experienced the issue. I used firebug to dig deeper and I did not see any errors in the console. I also noticed that the jason results returned from the API in firebug was only returning one website. So it may be a bug with the API... But in the API explorer it was returning fine. |
I also only see one response in the JSON using fiddler. From: RedTechie [mailto:[email protected]] I'm not by my workstation ATM. But I was using Firefox when I experienced the issue. I used firebug to dig deeper and I did not see any errors in the console. I also noticed that the jason results returned from the API in firebug was only returning one website. So it may be a bug with the API... But in the API explorer it was returning fine. — |
The fact that the websites are showing up in the API Explorer means the API is returning the correct response. The explorer is making ajax requests to the API just like manage.iis.net. Somehow the ajax request from manage.iis.net is getting cut short. |
Similar behavior has happened before that was being caused by an exception happening during the serialization of the response. If this is the case then the exception should appear in the API's logs. If you look in |
Yup there are some stack traces! 2016-10-13 18:15:02.814 -04:00 [Error] Connection id ""0HKVHSNFKM4SU"": An unhandled exception was thrown by the application. 2016-10-13 18:15:02.876 -04:00 [Error] Object reference not set to an instance of an object. |
Awesome, thank you so much for that. The stack trace tells us that there is a problem retrieving the bindings for the website. I'm going to try to repro this now. |
What is the bindings setup for your second website? |
I was able to reproduce this issue. If you create an https binding for a website that does not have a valid certificate mapped to the chosen port then this error will occur. If a site is created through the API there shouldn't be a way to get into this state. Did you create these sites through the API/manage.iis.net or some other method? Solution Until we fix the API to handle this state, the change will have to be done through INetMgr or https can be removed manually then added back with the API. Manually removing https |
Looking into this. But at first glance all of the certs are valid when viewed through Inetmgr. The bindings were created using Inetmgr. I have not tired creating any sites or objects using the API as of yet. One thing that does seem to be consistent is it's only affecting the sites with SSL bindings. EDIT: Actually scratch that... I just deleted the https binding from one of the sites (leaving only http) and its still not showing up with the same two stack traces. I know documentation is coming soon but what is this API command doing: https://SERVERIP:55539/api/webserver/websites?fields=name,status,physical_path,bindings,application_pool I'm assuming it's doing some sort of filtering? When I remove bindings from the request it outputs all the data fine. I also noticed that no "application_pool" data is being included in that request. Shouldn't it be? |
https://SERVERIP:55539/api/webserver/websites?fields=name,status,physical_path,bindings,application_pool queries all sites from the API and requests that the listed fields of the sites be displayed. The application_pool data isn't going to be displayed if this bug is occurring because the bug is terminating the JSON response. |
Also are the certificates on a Central Cert Store? |
Thank you again. There was actually multiple issues at play here. I found one and you have found another. Those bindings appear on the default web site if you have certain optional windows features enabled. For example, the picture below causes the net.tcp binding. Unfortunately we did not take into account other activation mechanisms and if those bindings are present then this error will occur. We will fix this for our next release. |
In your case "non http activation" should be the cause of net.tcp bindings appearing. They are there even when it is off? |
Yup, we randomly see them appear on some servers occasionally. We thought it was something to do with .NET re-registering itself or something but weren't exactly sure why we would randomly see them appear. |
I suspect my experience is the same issue. I built an app to allow our devs to proxy app pool cycling and noticed those weird mappings on one of the sites. I'm using the web.admin class and not json so it wasn't an issue and I just filtered out the odd bindings. Get Outlook for iOShttps://aka.ms/o0ukef On Thu, Oct 13, 2016 at 9:35 PM -0400, "RedTechie" <[email protected]mailto:[email protected]> wrote: Yup, we randomly see them appear on some servers occasionally. We thought it was something to do with .NET re-registering itself or something but weren't exactly sure why we would randomly see them appear. You are receiving this because you commented. |
Removed the odd bindings from my default site and now every other site appears as expected. Thanks! From: RedTechie [mailto:[email protected]] Yup, we randomly see them appear on some servers occasionally. We thought it was something to do with .NET re-registering itself or something but weren't exactly sure why we would randomly see them appear. — |
Linking related issues to follow their status: |
Re opening this issue until we release the updated API. |
Release is live, available at https://manage.iis.net/get. The GUI has been updated as well. |
When testing out the https://manage.iis.net interface it is only showing one website when the server and the API report multiple.
API Output:
Interface Output:
The text was updated successfully, but these errors were encountered: