Am I the only one who has troubles establishing a connection to the domain? In Firefox, I'm getting "Secure Connection Failed" and I can't see any certificate information... Using curl locally and also on one DO instance, I get the following: $ curl -v https://techblog.netflix.com/2016/08/vizceral-open-source.html * Trying 74.125.133.214... * Connected to techblog.netflix.com (74.125.133.214) port 443 (#0) * Server a…
Vizceral Open Source
11–20 of 32 posts
Re: Vizceral Open Source
#12Am I the only one who has troubles establishing a connection to the domain? In Firefox, I'm getting "Secure Connection Failed" and I can't see any certificate information... Using curl locally and also on one DO instance, I get the following: $ curl -v https://techblog.netflix.com/2016/08/vizceral-open-source.html * Trying 74.125.133.214... * Connected to techblog.netflix.com (74.125.133.214) port 443 (#0) * Server a…
link is to http, not https version
Re: Vizceral Open Source
#13Re: Vizceral Open Source
#14Re: Vizceral Open Source
#15Earlier quoted context omitted.
link is to http, not https version
I have the same issue, even though the link actually is http, my browser tries to open the https version, no matter what. It looks like https://netflix.com had hsts with includeSubdomains at one point in time which my browser has still cached.
Re: Vizceral Open Source
#16Am I the only one who has troubles establishing a connection to the domain? In Firefox, I'm getting "Secure Connection Failed" and I can't see any certificate information... Using curl locally and also on one DO instance, I get the following: $ curl -v https://techblog.netflix.com/2016/08/vizceral-open-source.html * Trying 74.125.133.214... * Connected to techblog.netflix.com (74.125.133.214) port 443 (#0) * Server a…
Re: Vizceral Open Source
#17Am I the only one who has troubles establishing a connection to the domain? In Firefox, I'm getting "Secure Connection Failed" and I can't see any certificate information... Using curl locally and also on one DO instance, I get the following: $ curl -v https://techblog.netflix.com/2016/08/vizceral-open-source.html * Trying 74.125.133.214... * Connected to techblog.netflix.com (74.125.133.214) port 443 (#0) * Server a…
Why did you add https? Just curious.
Thanks for the pointer :)
Re: Vizceral Open Source
#18This seems like it's a rendering layer for traffic data you're supposed to provide it. I'd love to have something I can get running more-or-less out of the box to collect and visualize traffic between my nodes on AWS, does anybody know of such a project?
(Disclosure: I work at sysdig)
Re: Vizceral Open Source
#19This seems like it's a rendering layer for traffic data you're supposed to provide it. I'd love to have something I can get running more-or-less out of the box to collect and visualize traffic between my nodes on AWS, does anybody know of such a project?
Re: Vizceral Open Source
#20Earlier quoted context omitted.
I have the same issue, even though the link actually is http, my browser tries to open the https version, no matter what. It looks like https://netflix.com had hsts with includeSubdomains at one point in time which my browser has still cached.
I have no problem opening https://netflix.com on Mozilla Firefox. But, the problem arises like what people said when opening Netflix techblog using https.