Title: Status Code 500
Last modified: December 23, 2019

---

# Status Code 500

 *  Resolved [Lens Digital](https://wordpress.org/support/users/lensdigital/)
 * (@lensdigital)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/status-code-500-2/)
 * I have uploaded and activated the plugin. When I navigate to the settings page,
   I get the following error;
 * Whoops, this is embarrassing
    Some unexpected error has occurred.
 * Request failed with status code 500
 * You might be able to find a solution to this problem in the plugin’s support 
   forum. If not, you could post about the problem there.
 * The server says:
    The site is experiencing technical difficulties. Please include
   this information if you submit an error report.
 * No other information.
 * Any clues where to start on debugging?

Viewing 1 replies (of 1 total)

 *  Plugin Author [mlwilkerson](https://wordpress.org/support/users/mlwilkerson/)
 * (@mlwilkerson)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/status-code-500-2/#post-12354451)
 * This is almost certainly the [same problem faced by others](https://wordpress.org/support/topic/request-failed-with-status-code-500/)
   who happen to have a combination of plugins installed that happen to trigger 
   a problem with how the currently released version of our plugin detects conflicts
   when you load the admin settings page.
 * I expect to be releasing fixes to this problem, along with a lot of other stuff,
   within the next couple of weeks.
 * In the meantime, you can find some additional debugging guidance on that other
   forum topic I linked. What you’d be looking for is to try and identify which 
   other plugin (or theme) is behaving unexpectedly, in a way that’s crashing our
   plugin. If you find that plugin, and you can live without it for now, then you
   can resolve this problem by deactivating that plugin.
 * If it’s not an option for you to deactivate that plugin, then another solution
   could be to drop our Font Awesome plugin and do a custom installation instead.
   [Here’s a tutorial](https://fontawesome.com/how-to-use/customizing-wordpress/intro/getting-started)
   on how you could do that. It’s more technical, and you’d lose some magic, but
   you could get it working for now, and then maybe try out the new version of the
   plugin when it’s released.
 * Once the forthcoming updates are released, I expect this problem to go away, 
   regardless of which other plugins you have active.

Viewing 1 replies (of 1 total)

The topic ‘Status Code 500’ is closed to new replies.

 * ![](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: [6 years, 2 months ago](https://wordpress.org/support/topic/status-code-500-2/#post-12354451)
 * Status: resolved