Juniper shared with me a few minutes ago that "one of the web servers filesystem went into a read-only, so we have removed that server from the cluster." That resolved the HTTPv6 around 9:45 pm Central and http://www.juniper.net now loads without issue on smartphones. The cert issue from smartphones when visiting https://juniper.net remains. That issue has probably been there for a long time. Frank From: Frank Bulk [mailto:frnkblk@iname.com] Sent: Saturday, January 04, 2014 9:30 PM To: 'Brad Cowie'; outages@outages.org Subject: RE: [outages] juniper.net 404 When testing from my Galaxy S III, I get a certificate error loading https://juniper.net, and a 404 when going to http://www.juniper.net. Does anyone have a mobile phone on IPv6, to see if they can see if they have a 404 with the v4 and v6 version of http://www.juniper.net? Frank From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Brad Cowie Sent: Saturday, January 04, 2014 5:45 PM To: outages@outages.org <mailto:outages@outages.org> Subject: Re: [outages] juniper.net 404 Hah yeah you're quite right Chuck. Works fine on my laptop but then when I switch to my phone (on the same wifi network) I get the 404. Must be attempting to redirect to a non-existent mobile version of http://juniper.net? Brad On 5 January 2014 12:37, Chuck Anderson <cra@wpi.edu <mailto:cra@wpi.edu> > wrote: I think this is a separate issue from the 404 error though. I can't load ANY of the variants, SSL or not, using a mobile device connected to the same network where I can successfully load the site using a desktop system. On Sat, Jan 04, 2014 at 03:26:03PM -0800, Conrad Heiney wrote:
Right they made this mistake with that particular URL only. I emailed a contact there. I'm sure it will be fixed shortly. All other url variants redirect to the https://www pattern which has a proper CA
On Saturday, January 4, 2014, Joe St Sauver wrote:
Hi,
Jeremy noted:
#Testing in a browser (Firefox) for https://juniper.net/ results in this: # #juniper.net <http://juniper.net> uses an invalid security certificate. #The certificate is not trusted because no issuer chain was provided. #(Error code: sec_error_unknown_issuer)
There are issues with more than just the cert. A more extensive analysis can be seen at:
https://www.ssllabs.com/ssltest/analyze.html?d=juniper.net
[FWIW, the SSL Labs tester is a tool I've previously recommended to folks in the higher ed community, e.g., as part of "SSL/TLS Certificiates: Giving Your Use of Server Certificates a Hard Look," http://pages.uoregon.edu/joe/hardlook/hard-look.pdf and most recently in "Networking in These Crazy Days: Stay Calm, Get Secure, Get Involved," http://pages.uoregon.edu/joe/merit-networking/merit-networking.pdf at slide 104. If you haven't checked your own site and critical sites you rely on, it can be eye opening to do so.]
Regards,
Joe
Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages