Support » Plugin: Font Awesome » Activation Failed

  • Resolved Henry Kozhaya

    (@henrykozhaya)


    Dear,
    I’m not able to activate Font Awesome Plugin in WordPress.
    Please find below the error i’m getting:
    Plugin could not be activated because it triggered a fatal error.
    The Font Awesome plugin caught a fatal error: Font Awesome could not be activated.
    Your WordPress server failed trying to send a request to the Font Awesome API server.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author mlwilkerson

    (@mlwilkerson)

    Hi Henry,

    Thanks for the report.

    First, are you running this WordPress server offline, or behind a firewall in some way that it would not be able to send a request over the internet to the Font Awesome API server? It is necessary for your WordPress server to contact the Font Awesome API server in order to activate the plugin, because the plugin has to load data about the available versions of Font Awesome.

    Could you also let me know which version of the plugin you’re using?

    Finally, when you see this error, there is probably also some additional diagnostic output in the browser console (also called Web console, or JavaScript console, depending on your browser). Could you let me know what other diagnostic information you find there about this error?

    Dear,
    My website is hosted and working perfectly. No firewall.
    WordPress version: 5.3.2
    Font Awesome version: 4.0.0-rc17

    Console log:
    Font Awesome Plugin Error Details
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=43c4fec879:1 message: Your WordPress server failed trying to send a request to the Font Awesome API server.
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=43c4fec879:1 stack trace:
    #0 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-metadata-provider.php(122): FortAwesomeFontAwesome_Exception::with_wp_error(Object(WP_Error))
    #1 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(255): FortAwesomeFontAwesome_Metadata_Provider->metadata_query('query {
    latest…', true)
    #2 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(152): FortAwesomeFontAwesome_Release_Provider->query('query {
    latest…')
    #3 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome.php(622): FortAwesomeFontAwesome_Release_Provider->load_releases()
    #4 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(66): FortAwesomeFontAwesome->refresh_releases()
    #5 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(48): FortAwesomeFontAwesome_Activator::initialize_user_options()
    #6 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(24): FortAwesomeFontAwesome_Activator::initialize()
    #7 /home/www/lazordyco.com/wp-content/plugins/font-awesome/font-awesome.php(255): FortAwesomeFontAwesome_Activator::activate()
    #8 /home/www/lazordyco.com/wp-includes/class-wp-hook.php(288): FortAwesomeFontAwesome_Loader->activate_plugin('')
    #9 /home/www/lazordyco.com/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters('', Array)
    #10 /home/www/lazordyco.com/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #11 /home/www/lazordyco.com/wp-admin/plugins.php(177): do_action('activate_font-a…')
    #12 {main}

    Other plugins installed:

    • Akismet Anti-Spam
    • Album and Image Gallery Plus Lightbox
    • Anti-Spam
    • Elementor
    • Ninja Forms
    • Official Facebook Pixel
    • Under Construction
    • Yoast SEO

    Theme used: Velux – Version: 1.1.3

    Best regards.

    Plugin Author mlwilkerson

    (@mlwilkerson)

    Thank you. Unfortunately that console log is missing the crucial information I need for troubleshooting. This has helped me to realize that some additional logging needed to be added. I’ve just released 4.0.0-rc18 that includes the additional error logging. Could you update to that version and try again? I expect it to fail in the same way, but also for the console to include some additional information. If you could share the new console log error messages with me, that would be helpful.

    Hi Dear,
    I appreciate your help. Below the new console log:
    message: Your WordPress server failed trying to send a request to the Font Awesome API server.
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=a4ec738193:1 stack trace:
    #0 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-metadata-provider.php(122): FortAwesomeFontAwesome_Exception::with_wp_error(Object(WP_Error))
    #1 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(255): FortAwesomeFontAwesome_Metadata_Provider->metadata_query('query {
    latest…', true)
    #2 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(152): FortAwesomeFontAwesome_Release_Provider->query('query {
    latest…')
    #3 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome.php(622): FortAwesomeFontAwesome_Release_Provider->load_releases()
    #4 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(66): FortAwesomeFontAwesome->refresh_releases()
    #5 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(48): FortAwesomeFontAwesome_Activator::initialize_user_options()
    #6 /home/www/logicempower.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(24): FortAwesomeFontAwesome_Activator::initialize()
    #7 /home/www/logicempower.com/wp-content/plugins/font-awesome/font-awesome.php(255): FortAwesomeFontAwesome_Activator::activate()
    #8 /home/www/logicempower.com/wp-includes/class-wp-hook.php(288): FortAwesomeFontAwesome_Loader->activate_plugin('')
    #9 /home/www/logicempower.com/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters('', Array)
    #10 /home/www/logicempower.com/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #11 /home/www/logicempower.com/wp-admin/plugins.php(177): do_action('activate_font-a…')
    #12 {main}
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=a4ec738193:1 WP_Error Object
    (
    [errors] => Array
    (
    [http_request_failed] => Array
    (
    [0] => cURL error 7:
    )

    )

    [error_data] => Array
    (
    )

    )

    Many thanks

    Plugin Author mlwilkerson

    (@mlwilkerson)

    Unfortunately, that error message “cURL error 7” doesn’t provide much detail, but it’s at least a clue.

    I’ve just released 4.0.0-rc19 with even more diagnostic output. If you would try that one in the same way and report its console output, that would be helpful.

    Dear,
    Thank you again; below the output of the console:
    —-
    message: Your WordPress server failed trying to send a request to the Font Awesome API server.
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 stack trace:
    #0 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-metadata-provider.php(122): FortAwesomeFontAwesome_Exception::with_wp_error(Object(WP_Error))
    #1 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(255): FortAwesomeFontAwesome_Metadata_Provider->metadata_query(‘query {
    latest…’, true)
    #2 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-release-provider.php(152): FortAwesomeFontAwesome_Release_Provider->query(‘query {
    latest…’)
    #3 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome.php(622): FortAwesomeFontAwesome_Release_Provider->load_releases()
    #4 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(66): FortAwesomeFontAwesome->refresh_releases()
    #5 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(48): FortAwesomeFontAwesome_Activator::initialize_user_options()
    #6 /home/www/lazordyco.com/wp-content/plugins/font-awesome/includes/class-fontawesome-activator.php(24): FortAwesomeFontAwesome_Activator::initialize()
    #7 /home/www/lazordyco.com/wp-content/plugins/font-awesome/font-awesome.php(255): FortAwesomeFontAwesome_Activator::activate()
    #8 /home/www/lazordyco.com/wp-includes/class-wp-hook.php(288): FortAwesomeFontAwesome_Loader->activate_plugin(”)
    #9 /home/www/lazordyco.com/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(”, Array)
    #10 /home/www/lazordyco.com/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #11 /home/www/lazordyco.com/wp-admin/plugins.php(177): do_action(‘activate_font-a…’)
    #12 {main}
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 WP_Error
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 code: http_request_failed
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 message: cURL error 7:
    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 data:
    curl loaded: true
    curl version_number: 474112
    curl features: 4162461
    curl ssl_version_number: 0
    curl version: 7.60.0
    curl host: x86_64-redhat-linux-gnu
    curl ssl_version: NSS/3.34
    openssl loaded: true
    openssl cipher methods: AES-128-CBC,AES-128-CBC-HMAC-SHA1,AES-128-CBC-HMAC-SHA256,AES-128-CFB,AES-128-CFB1,AES-128-CFB8,AES-128-CTR,AES-128-ECB,AES-128-OFB,AES-128-XTS,AES-192-CBC,AES-192-CFB,AES-192-CFB1,AES-192-CFB8,AES-192-CTR,AES-192-ECB,AES-192-OFB,AES-256-CBC,AES-256-CBC-HMAC-SHA1,AES-256-CBC-HMAC-SHA256,AES-256-CFB,AES-256-CFB1,AES-256-CFB8,AES-256-CTR,AES-256-ECB,AES-256-OFB,AES-256-XTS,BF-CBC,BF-CFB,BF-ECB,BF-OFB,CAMELLIA-128-CBC,CAMELLIA-128-CFB,CAMELLIA-128-CFB1,CAMELLIA-128-CFB8,CAMELLIA-128-ECB,CAMELLIA-128-OFB,CAMELLIA-192-CBC,CAMELLIA-192-CFB,CAMELLIA-192-CFB1,CAMELLIA-192-CFB8,CAMELLIA-192-ECB,CAMELLIA-192-OFB,CAMELLIA-256-CBC,CAMELLIA-256-CFB,CAMELLIA-256-CFB1,CAMELLIA-256-CFB8,CAMELLIA-256-ECB,CAMELLIA-256-OFB,CAST5-CBC,CAST5-CFB,CAST5-ECB,CAST5-OFB,DES-CBC,DES-CFB,DES-CFB1,DES-CFB8,DES-ECB,DES-EDE,DES-EDE-CBC,DES-EDE-CFB,DES-EDE-OFB,DES-EDE3,DES-EDE3-CBC,DES-EDE3-CFB,DES-EDE3-CFB1,DES-EDE3-CFB8,DES-EDE3-OFB,DES-OFB,DESX-CBC,IDEA-CBC,IDEA-CFB,IDEA-ECB,IDEA-OFB,RC2-40-CBC,RC2-64-CBC,RC2-CBC,RC2-CFB,RC2-ECB,RC2-OFB,RC4,RC4-40,RC4-HMAC-MD5,RC5-CBC,RC5-CFB,RC5-ECB,RC5-OFB,SEED-CBC,SEED-CFB,SEED-ECB,SEED-OFB,aes-128-cbc,aes-128-cbc-hmac-sha1,aes-128-cbc-hmac-sha256,aes-128-ccm,aes-128-cfb,aes-128-cfb1,aes-128-cfb8,aes-128-ctr,aes-128-ecb,aes-128-gcm,aes-128-ofb,aes-128-xts,aes-192-cbc,aes-192-ccm,aes-192-cfb,aes-192-cfb1,aes-192-cfb8,aes-192-ctr,aes-192-ecb,aes-192-gcm,aes-192-ofb,aes-256-cbc,aes-256-cbc-hmac-sha1,aes-256-cbc-hmac-sha256,aes-256-ccm,aes-256-cfb,aes-256-cfb1,aes-256-cfb8,aes-256-ctr,aes-256-ecb,aes-256-gcm,aes-256-ofb,aes-256-xts,bf-cbc,bf-cfb,bf-ecb,bf-ofb,camellia-128-cbc,camellia-128-cfb,camellia-128-cfb1,camellia-128-cfb8,camellia-128-ecb,camellia-128-ofb,camellia-192-cbc,camellia-192-cfb,camellia-192-cfb1,camellia-192-cfb8,camellia-192-ecb,camellia-192-ofb,camellia-256-cbc,camellia-256-cfb,camellia-256-cfb1,camellia-256-cfb8,camellia-256-ecb,camellia-256-ofb,cast5-cbc,cast5-cfb,cast5-ecb,cast5-ofb,des-cbc,des-cfb,des-cfb1,des-cfb8,des-ecb,des-ede,des-ede-cbc,des-ede-cfb,des-ede-ofb,des-ede3,des-ede3-cbc,des-ede3-cfb,des-ede3-cfb1,des-ede3-cfb8,des-ede3-ofb,des-ofb,desx-cbc,id-aes128-CCM,id-aes128-GCM,id-aes128-wrap,id-aes128-wrap-pad,id-aes192-CCM,id-aes192-GCM,id-aes192-wrap,id-aes192-wrap-pad,id-aes256-CCM,id-aes256-GCM,id-aes256-wrap,id-aes256-wrap-pad,id-smime-alg-CMS3DESwrap,idea-cbc,idea-cfb,idea-ecb,idea-ofb,rc2-40-cbc,rc2-64-cbc,rc2-cbc,rc2-cfb,rc2-ecb,rc2-ofb,rc4,rc4-40,rc4-hmac-md5,rc5-cbc,rc5-cfb,rc5-ecb,rc5-ofb,seed-cbc,seed-cfb,seed-ecb,seed-ofb

    plugins.php?action=error_scrape&plugin=font-awesome%2Findex.php&_wpnonce=895a2786c3:1 php version: 7.3.15
    WordPress version: 5.3.2
    multisite: false
    is_network_admin: false

    Best regards.

    Plugin Author mlwilkerson

    (@mlwilkerson)

    OK, this output seems to just confirm that your PHP environment has a curl configuration that should be able to make a secure connection to api.fontawesome.com. It would need to be able to do TLSv1.1 or TLSv1.2, and as far as I can tell, yours should (using NSS/3.34). It also includes cipher methods that our server can support.

    The curl error 7 is just saying that the connection is failing for some reason. I think we can rule out the S from https as a reason for that: your server should be able to make a secure connection.

    That seems to lead back to my initial guess, which is some kind of firewall filter. Maybe your hosting provider, or their upstream network provider has some reason for blocking access to api.fontawesome.com?

    Sometimes we’ve seen Internet Service Providers mistakenly block our IP addresses due to overly aggressive security policies. I don’t know why that might be the case here, but unfortunately, my ability to help troubleshoot your server and network is limited.

    Do you have shell access to your web server? If so, you could run the following curl command on a shell prompt to help verify whether your WordPress host server is able to make a connection to api.fontawesome.com. If it fails, it may also provide more specific error information. If you don’t have shell access, you could offer this curl command to your web host provider or system administrator to help with troubleshooting.

    You should be able to run this:

    curl -H "Content-Type: application/json" --data '{ "query": "{ release(version: \"latest\") { version } }" }' https://api.fontawesome.com

    and see a response like this:

    {"data":{"release":{"version":"5.12.1"}}}

    @mlwilkerson Many thanks really!
    We solved the problem, I contacted my hosting. There was some blocked IP from their side!
    Many thanks

    Plugin Author mlwilkerson

    (@mlwilkerson)

    Great!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.