Title: CORS Error
Last modified: August 8, 2026

---

# CORS Error

 *  [Francesco](https://wordpress.org/support/users/francy27/)
 * (@francy27)
 * [6 days, 8 hours ago](https://wordpress.org/support/topic/cors-error-17/)
 * Hi, 
   I use this plugin on almost every website I built with WordPress and it 
   always worked just fine.
 * After the update I noticed this error in the Console, and my website is now without
   icons!
 *     ```wp-block-code
       Access to CSS stylesheet at 'https://use.fontawesome.com/releases/v7.3.1/css/all.css' from origin 'https://ifivending.it' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.all.css:1  Failed to load resource: net::ERR_FAILED
       ```
   
 * The website is now under construction, I use the Kadence theme and few other 
   plugins.
 * Can you help me? Thank you
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcors-error-17%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Author [mlwilkerson](https://wordpress.org/support/users/mlwilkerson/)
 * (@mlwilkerson)
 * [4 days ago](https://wordpress.org/support/topic/cors-error-17/#post-18989677)
 * Hello, [@francy27](https://wordpress.org/support/users/francy27/) . I took a 
   look at that site, and it appears to be loading Font Awesome now from cdnjs.cloudflare.
   com instead of use.fontawesome.com, and I don’t see that CORS error. Did you 
   perhaps switch how you load Font Awesome since you posted this?
 * Anyway, I’d need a little more information in order to investigate. I don’t yet
   know of a reason why any updates of the Font Awesome plugin would cause _that_
   error on _that_ URL.
 * Often a CORS error like that is a red herring. There’s often an underlying error
   that’s there, and the CORS error is caused by the response of that underlying
   error not having the correct CORS headers. So to understand the actual cause,
   I’d need to investigate to see that that underlying error is.
 * So you could dig to find that in the browser’s network tab, or point me to a 
   staging site, for example, where the error still occurs, and I could investigate
   there.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcors-error-17%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/font-awesome/assets/icon-256x256.png?rev=1991998)
 * [Font Awesome](https://wordpress.org/plugins/font-awesome/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/font-awesome/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/font-awesome/)
 * [Active Topics](https://wordpress.org/support/plugin/font-awesome/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/font-awesome/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/font-awesome/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [mlwilkerson](https://wordpress.org/support/users/mlwilkerson/)
 * Last activity: [4 days ago](https://wordpress.org/support/topic/cors-error-17/#post-18989677)
 * Status: not resolved