Sorry I forgot to reply to this. Remove the https binding against the IP unless you are trying to support old clients like Windows XP (in which case remove the old https binding).
So each full hostname should have 1 http binding (optionally) and 1 https binding (only).
The IP specific binding will actually take precedence over any request to the server for any website if it ends up coming in on that IP address (which it probably does), so then you run into the possibility of serving the wrong certificate.
In general, IP specific bindings are a recipe for pain on Windows unless you have a distinct requirement for them. A specific IP per certificate used to be required on Server 2008 and lower but then they introduced SNI (server name indication) which takes the hostname of the site your trying to access and presents the correct certificate (if the https binding for the site has SNI switched on, and has no specific IP).
My recommendation: ensure you only have one https binding in IIS per hostname (e.g. pixel8.net) and ensure it is has IP set to (All Unassigned) or *, and SNI is enabled. Then check your site using an ssl checker like this one: https://www.ssllabs.com/ssltest