4 ms·

I'm not expert on this but what I'm seeing is that port 443 is serving up a response when jaruzel.com is requested on that port. While you may not be actively a

I'm not expert on this but what I'm seeing is that port 443 is serving up a response when jaruzel.com is requested on that port. While you may not be actively advertising that domain with https URLs, it is valid for clients to request one speculatively. There isn't a valid cert for that domain and for some reason for server is offering a different one. Presumably you need to unbind 443 from that host header name (this is based on memories of configuring IIS a decade ago).

na85 9y ago
Complaining about a non-existent SSL cert and then backseat driving the "fix", using words like "you need to", all based on shady memories of configuring IIS a decade ago? Really?
- Spare_account 9y ago
  Just having a chat about it really, sorry it rubbed you up the wrong way.
  - Jaruzel 9y ago
    I'm cool with it. I like these sort of side-bar conversations.
zer0t3ch 9y ago
"port 443 is serving up a response when jaruzel.com is requested on that port" The only response is a 404, which is exactly what should be displayed (to the best of my knowledge) for a domain that isn't configured for that IP/port when there are other sites utilizing that IP/port.
- Spare_account 9y ago
  Oh dear, this hasn't gone very well has it. I'll have another look when I'm home, I thought I was closer to the mark. Thank you for the response.
Jaruzel 9y ago
So... I have an IP... that IP points to a router, that router port-forwards ports 80 and 443 blindly to a web server, on that web server is a bunch of websites. IIS knows which ones to serve to clients based on a) the host-header, and b) the port. jaruzel.com:443 is not valid, but because I run an older version of IIS[1], that does not support SNI, the cert is bound to the port, not the host-header. As such any domain name that points to the IP will dump you at that cert if you try to connect on port 443. Hope this clears up any confusion. :) --- [1] for um... reasons.
- Spare_account 9y ago
  Thank you, I appreciate the detailed response :-)

na85 9y ago

Complaining about a non-existent SSL cert and then backseat driving the "fix", using words like "you need to", all based on shady memories of configuring IIS a decade ago? Really?

Spare_account 9y ago
Just having a chat about it really, sorry it rubbed you up the wrong way.
- Jaruzel 9y ago
  I'm cool with it. I like these sort of side-bar conversations.

zer0t3ch 9y ago

"port 443 is serving up a response when jaruzel.com is requested on that port" The only response is a 404, which is exactly what should be displayed (to the best of my knowledge) for a domain that isn't configured for that IP/port when there are other sites utilizing that IP/port.

Spare_account 9y ago
Oh dear, this hasn't gone very well has it. I'll have another look when I'm home, I thought I was closer to the mark. Thank you for the response.

Jaruzel 9y ago

So... I have an IP... that IP points to a router, that router port-forwards ports 80 and 443 blindly to a web server, on that web server is a bunch of websites. IIS knows which ones to serve to clients based on a) the host-header, and b) the port. jaruzel.com:443 is not valid, but because I run an older version of IIS[1], that does not support SNI, the cert is bound to the port, not the host-header. As such any domain name that points to the IP will dump you at that cert if you try to connect on port 443. Hope this clears up any confusion. :) --- [1] for um... reasons.

Spare_account 9y ago
Thank you, I appreciate the detailed response :-)