# 404 Fontawsome issue

**URL:** <https://community.wpbeaverbuilder.com/t/404-fontawsome-issue/18032>\
**Category:** Beaver Builder\
**Tags:** beaver-builder\
**Created:** [December 9, 2023, 1:47am UTC](https://community.wpbeaverbuilder.com/t/404-fontawsome-issue/18032 "2023-12-09T01:47:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![redwineMAn](https://community.wpbeaverbuilder.com/letter_avatar_proxy/v4/letter/r/13edae/32.png) [@redwineMAn](https://community.wpbeaverbuilder.com/u/redwineMAn)\
**Post date:** [December 9, 2023, 1:47am UTC](https://community.wpbeaverbuilder.com/t/404-fontawsome-issue/18032/1 "2023-12-09T01:47:36Z")

</div>

We seem to be getting a large amount of 404 errors relating to the following

/wp-content/plugins/bb-plugin/fonts/fontawesome/5.15.1/webfonts/fa-regular-400.woff2  
/wp-content/plugins/bb-plugin/fonts/fontawesome/5.15.1/webfonts/fa-solid-900.woff2

The fontawsome folder on our sites has 5.15.4 (not 5.15.1)  
How can I prevent these errors or identify where the request is originating

---

<div class="post-metadata">

**Author:** ![pross](https://community.wpbeaverbuilder.com/user_avatar/community.wpbeaverbuilder.com/pross/32/883_2.png) [@pross](https://community.wpbeaverbuilder.com/u/pross)\
**Post date:** [December 9, 2023, 3:57pm UTC](https://community.wpbeaverbuilder.com/t/404-fontawsome-issue/18032/2 "2023-12-09T15:57:52Z")

</div>

Restart php service you are overoptimising and storing the PATH in memory restarting the service will force php to use the correct PATH