• Resolved Pierre

    (@uptoyou)


    Hi there,

    We have made the update to the latest version for Better Font Awesome
    and now we keep having this issue.

    API Error
    The attempt to reach the jsDelivr API server failed with the following error: http_request_failed: cURL error 28: Connection timed out after 10001 milliseconds (URL: https://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)

    Don’t worry! Better Font Awesome will still render using the included fallback version: 4.7.0

    Your support is appreciated.
    Thank you so much, Team!

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 17 total)
  • node2

    (@node2)

    Also having this problem.
    Kind regards!

    acmdesigns

    (@acmdesigns)

    jumping on this. Having the same problem and it’s massively slowing down one of my sites. Disabling this plugin dropped my page load times from ~20seconds to about 1-2 seconds.

    • This reply was modified 4 years ago by acmdesigns.
    silva8899

    (@silva8899)

    Me too, my newspaper website is yet terrible slow! When this will be fixed?!

    Plugin Author Mickey Kay

    (@mcguive7)

    So sorry y’all, but it looks like this is an issue with the jsdelivr CDN that hosts font awesome, and is not something I have any control over. If you really need to get a fix out, you can always try the latest beta that I’m hoping to release in the near future. If you’re interested, please see https://www.ads-software.com/support/topic/bfa-2-with-wp-5-6-compatibility-ready-for-testing/

    marcrix

    (@marcrix)

    Hi, I have the same plugin and performance issues.
    I hope you will fix it soon…

    Uschi59

    (@uschi59)

    Same problem here… Again and again.

    mariusvw

    (@mariusvw)

    @mcguive7 maybe an idea to lower the timeout for this call to 3 seconds instead of the PHP default which can be 30 seconds.

    Seems their API service is currently unreachable from several locations.

    silva8899

    (@silva8899)

    Hi @mcguive7
    i tried your Beta Version and this doesn’t work fine. The shortcode does not appear this icon ( Screenshot: https://prnt.sc/10882ta )

    when i activated your plugin shows like this ( screenshot: https://prnt.sc/10883qo )

    so long that this is not fixed, i cant activate your Plugin!!!

    best regards

    ktsiterip

    (@ktsiterip)

    Not a permamnent fix, but the solution (try at your own risk – seems to work for me) at
    https://www.ads-software.com/support/topic/better-font-awesome-api-error-3/
    seems to solve the issue

    In the file:
    wp-content\plugins\better-font-awesome\vendor\mickey-kay\better-font-awesome-library\better-font-awesome-library.php

    Change / comment out line 238 from
    $this->setup_api_data();
    to
    //$this->setup_api_data();

    Thanks to @xberg for their post 11 months ago

    • This reply was modified 4 years ago by ktsiterip.
    mappel

    (@mappel)

    yes, my site is super slow since this morning, too… even the wp dashboard ect backend is affected… tried to upload new images and it took forever…

    API Error
    The attempt to reach the jsDelivr API server failed with the following error: http_request_failed: cURL error 28: Connection timed out after 10000 milliseconds (URL: https://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)

    Plugin Author Mickey Kay

    (@mcguive7)

    Hi all, I got in touch with the CDN and confirmed they were down and were able to get things back up and running. The issue at hand should resolve shortly, if it hasn’t already. Thanks for all the feedback, and definitely a good idea to lower the timeout on the data fetch. I will be working on integrating that adjustment in the coming week, ideally in conjunction with the bigger 2.0 release that we have been beta testing. Thanks everyone for your feedback and patience.

    acmdesigns

    (@acmdesigns)

    Can confirm, performance issues are no longer present with Better Font Awesome plugin enabled. Thank you for following up on this Mickey.

    The timeout definitely needs to be lowered to a reasonable level. It was frustrating having severe performance issues without knowing the cause of it. For a while the site was very slow but without the timeout error displaying. I would assume that the timeout wasn’t being hit, but the CDN was still taking a significant amount of time.

    silva8899

    (@silva8899)

    me too, can confirm…everything works again fine

    mariusvw

    (@mariusvw)

    @mcguive7 all stable online again, thanks for the quick response and future fixes. ??

    Thread Starter Pierre

    (@uptoyou)

    Thanks Mickey!

    I confirm we back in business.
    Thank’s for your precious support!

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘The attempt to reach the jsDelivr API server failed’ is closed to new replies.