Craig Wilson

My feedback

  1. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Craig Wilson commented  · 

    Similar issue for me in 1801 Web Console, When trying to login I got an "Underlying Connection was closed" error.

    To cut a long story short, this only happened across HTTPS, and after much hair pulling and console re-installs, the problem was found to be the IIS binding..

    Specifically, I had an IP bound to port 443, but as soon as I bound it to all IPs it started working on HTTPS

    So instead of <server-ip-address>:443
    I changed it to *:443

    Weird, but it works!

  2. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Craig Wilson shared this idea  · 
  3. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Craig Wilson shared this idea  · 
  4. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Craig Wilson commented  · 

    I got a similar issue with the web console over SSL
    I could access it fine over HTTP:// but got "Underlying connection was closed" error when trying over HTTPS://
    After much investigation I managed to fix it by changing my IIS Binding for HTTPS
    FROM: <serverip>:443
    TO *:443

    Not sure as to the reason why as this was fine in SCOM 2016...

Feedback and Knowledge Base