Font-awesome: use.fontawesome.com HTTPS error

[cylkee]

Icons not displayed. Found cause:

use.fontawesome.com uses an invalid security certificate.The certificate expired on 15 June 2017 at 13:00. The current time is 15 June 2017 at 13:23.Error code: SEC_ERROR_EXPIRED_CERTIFICATE

If I download the .js and generated .css over HTTP and use these files, icons appear as normal.

Tested in Firefox 53.

[connormcwood]

https://use.fontawesome.com/d3539ca1f0.js

Came to say this. Favicon icon has been removed or disappeared.

Failed to load resource: the server responded with a status of 403 () favicon.ico

Solution:

1. Download FontAwesome http://fontawesome.io/#modal-download
2. Add Css/Fontawesome.min.css & Fonts/ directory
3. Remove .js and add a stylesheet path to the added font awesome directory
4. Error(s) should go, icons should work and site should be HTTPS again

[JamesMPrince]

Same for us. Icons not appearing, using CDN method.

[jg2703]

Same again... sorry just typing out my issue!!

[lordcoste]

Same here.

[JamesMPrince]

Downloading them fixes the issue, but not ideal.

[gasulliv]

That sucks, but at least there is a work around! Thanks for letting us know, hopefully the CDN will be back up soon!!

[JamesMPrince]

I think they're back now?!

[jg2703]

Looks like they're up and running now, I checked the certificate

[gasulliv]

awesome! Let me check it out!

[Stereoide]

Yup, back up again. Thanks!

[tagliala]

@robmadole could you please confirm that everything is fine?

[robmadole]

This is resolved now. Sorry about that folks.

[tf-venegas10]

It happened again...

[brunopardim]

Hi Fort Awesome
Team,

It happened again this problem.

I'm using kit.

Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID
kit-free.fontawesome.com/releases/latest/css/free-v4-font-face.min.css:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID
kit-free.fontawesome.com/releases/latest/css/free.min.css:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID
kit-free.fontawesome.com/releases/latest/css/free-v4-shims.min.css:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID
kit-free.fontawesome.com/releases/latest/css/free-v4-font-face.min.css:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID
kit-free.fontawesome.com/releases/latest/css/free.min.css:1 Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID

[tagliala]

Hi, thanks for reporting this. We are aware of the situation and StackPath, our CDN provider, is pushing a fix.

Quoting from: https://status.stackpath.com/incidents/22c999cbl1nh

We have begun rolling out an update that will resolve the ongoing SSL errors StackPath customers are experiencing. We will continue to provide updates as this process continues forward.

Ref:

• https://status.stackpath.com/incidents/22c999cbl1nh
• https://status.fortawesome.com/

[brunopardim]

Hi, thanks for reporting this. We are aware of the situation and StackPath, our CDN provider, is pushing a fix.

Quoting from: https://status.stackpath.com/incidents/22c999cbl1nh

We have begun rolling out an update that will resolve the ongoing SSL errors StackPath customers are experiencing. We will continue to provide updates as this process continues forward.

Ref:

* https://status.stackpath.com/incidents/22c999cbl1nh

* https://status.fortawesome.com/

Tks @tagliala :)

[mengnans]

Today it happens to one of my clients, it happens on her home laptop and work desktop.
Not sure how is it triggered, cuz everyone else is not having this issue.
Confirmed she doesn't have extensions, no VPN.
I am starting to think should I download the min.css and put it into our server.
Doesn't sound ideal.