Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAngular.io Website SSL Certificate Problem #1875
Comments
|
I have the same issue, it's related to the certificate for firebase (which is the same for angular.io), you probably have the same issue with https://www.firebase.com/ |
|
I think it's related to the number of 'questionable quality' sites listed on certificate. https://www.sslshopper.com/ssl-checker.html#hostname=angular.io Angular should get their own certificate to sidestep the problem. |
|
Yes, that's a good idea, and for firebase as well, it should be an official and exclusive google certificate |
|
Same issue here. ESET NOD32 was the culprit. |
|
Turn off SSL filtering solved it |
|
I also had the same issue. Angular.io seems is so far the only site I've encountered this. I can access it on my mobile on the same network without any problems. |
|
It's also possible to load the website under ESET NOD32 by disabling HTTPS scanning (guessing it's almost the same thing?) |
|
For those who would rather only allow access for the certificate used by angular.io, you can |
|
It appears this problem can be extended to those using FortiGate firewalls. Note sure if there is a work around for this at this time. |
|
Indeed, I am behind a FortiGate Firewall and can't access any page under https://angular.io Anyone knows if the tutorials are available elsewhere? |
|
You can build the repo locally: https://github.com/angular/angular.io |
|
I'm actually trying that @ocombe but when I do my gulp server-and-sync the Chrome tab that is trying to load it just spins for forever. I've realized that's because I don't have things setup properly but the next hurdle is the Python requirement. Quite a pain just to read some documentation. |
|
Today I can't access angular.io using Chrome. I get this message: |
|
@marcusreese that's unusual. Is it still occurring, or was it temporary? |
|
it's still occurring to all of us who use those firewalls / antivirus softwares |
|
I had our security people do some config changes to allow access but the firebase CDN IP changed yesterday so that broke that. It's looking like we either need to spend time/effort replicating the documentation locally or find another framework to use. I'm wondering how many other Enterprises (who would be the more likely consumers of Fortigate firewalls) are going to have the same choice because of one silly SSL certificate. |
|
@jeffbcross I can show you the problem at angular connect next week if you want |
|
Same problem for me.... and impossible to modify the FortiGate Firewall of the place where is my entreprise..... and we are working with angular.... so it's very very difficult to can get access to documentation :-(. |
|
To all of you who struggle to access the documentation, it is also available on devdocs: http://devdocs.io/angular~2.0_typescript/ |
|
I'm also in contact with Firebase to see if they can fix anything on there side as this issue impacts all the sites on that SSL certificate. |
|
@ocombe Images aren't working as per http://devdocs.io/angular~2.0_typescript/cookbook/component-communication Not sure if that's something that can be resolved or where I'd report it but still a nice workaround for now. |
|
Same issue here, I as well am behind a FortiGate firewall |
|
Same issue here as well - behind a FortiGate firewall. EDIT: Should add that, like Shane above, the change of CDN IP broke the firewall rule we previously had in place that was working. |
|
Same issue. Both Bitdefender and ESET won't allow for a connection to be made. This is critical for us, because we need to access the site. |
|
It works, thanks. P.S. |
|
Works behind a Fortigate firewall now! Thanks very much! |
|
Well, it seems like the new cert worked! I'll close this issue now. If anyone experiences a similar issue, please create a new issue and mention me in it. |
|
And big thanks to @mbleigh for taking care of this! |
|
@mbleigh this does mean that all/most other firebase hosting customers are dealing with the same unreachability though... |
|
We're working on a solution for everyone. Consider this a small test of On Tue, Nov 8, 2016, 7:27 AM Jonas De Kegel notifications@github.com
|
|
@jeffbcross @mbleigh My company cannot access the site due to our third party firewall declaring the cert bad. The initial October fix seemed to work, though problems recurred a couple weeks ago. I'm not sure I can help by opening a new issue because I won't be able to verify resolution (we can't do without the site any longer and will simply be whitelisting it by close of business today). |
|
I'm not sure why Github says I unassigned @jeffbcross |
|
Dan: are you able to send me information about the certificate you're
seeing? Specifically the Common Name, Subject Alternate Names, and
expiration date?
…On Thu, Feb 2, 2017 at 11:43 AM Dan Wolf ***@***.***> wrote:
I'm not sure why Github says I unassigned @jeffbcross
<https://github.com/jeffbcross>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1875 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAD_vqw3HjC44MfeZTRjiyqHsBRneJ5ks5rYi23gaJpZM4JLLor>
.
|
|
The issue is back for me as well, haven't visited angular.io in a while though so I don't know when it began again.
… On Feb 2, 2017, at 1:48 PM, Michael Bleigh ***@***.***> wrote:
Dan: are you able to send me information about the certificate you're
seeing? Specifically the Common Name, Subject Alternate Names, and
expiration date?
On Thu, Feb 2, 2017 at 11:43 AM Dan Wolf ***@***.***> wrote:
> I'm not sure why Github says I unassigned @jeffbcross
> <https://github.com/jeffbcross>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1875 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAAD_vqw3HjC44MfeZTRjiyqHsBRneJ5ks5rYi23gaJpZM4JLLor>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
No problem for me, it's still working |
|
Actually, I'm seeing angular.io serving from a shared certificate again.
I'll investigate and report back.
…On Thu, Feb 2, 2017 at 12:21 PM Olivier Combe ***@***.***> wrote:
No problem for me, it's still working
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1875 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAD_usi0F7vnNMQcE5eA58Cd-O9vKKwks5rYjlSgaJpZM4JLLor>
.
|
|
Stopped working for me as well. |
|
Started experiencing the same symptoms again as @rodp82 |
|
I am facing the same problems, but as rodp82 said, turning of ssl scanning in bitdefender does the trick. |
|
For me in my company it complains that the TLS 1.0 to TLS 1.2 is deactivated. Probably for security reasons so the angular.* stack needs to be upped to the next level for us to be able to access the site. |
|
We have an idea of what's causing this, but the fix is going to take a
little while. Please bear with us, and apologies for the inconvenience.
…On Wed, Feb 8, 2017 at 12:27 PM Fredric Adell ***@***.***> wrote:
For me in my company it complains that the TLS 1.0 to TLS 1.2 is
deactivated. Probably for security reasons so the angular.* stack needs to
be upped to the next level for us to be able to access the site.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1875 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAD_oamkvVGGUzx6RfAKcsZ58TmjFKvks5raiU8gaJpZM4JLLor>
.
|
|
Any update on this? Still experiencing cert errors as of today. |
|
I am having this same exact problem using Chrome on Windows 10 Professional 64 bit. I get basically the same error when trying it with Firefox.
Chrome: Firefox: |
|
Hi, |
|
Hey all, can you give this another spin? We are no longer serving the same GlobalSign certificate and this may be resolved. Please let me know if you're still having problems! |
|
It seems that I can get to it just fine now.
… On Mar 30, 2017, at 2:53 PM, Michael Bleigh ***@***.***> wrote:
Hey all, can you give this another spin? We are no longer serving the same GlobalSign certificate and this may be resolved. Please let me know if you're still having problems!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Appears to be fixed with Bitdefender too. Working now. Thanks! |
|
Yes! It's working now. Thanks. |
|
Works fine with ESET, thanks :) |
|
Works fine now! Thanks. |
|
Works fine with à firewall. Thanks. |
and others
The angular.io website does not work with ESET NOD32, I believe there is a certificate problem.
The certificate has many spam sites in the SAN field.
In NOD32 I have to "Disable HTTPS checking" to view the site or it is blocked.
This happens on no other sites that I visit regularly.