jsDelivr API server failed

  • rslater_illinois

    (@rslater_illinois)


    5 years, 3 months ago

    I am getting dashboard errors:

    “Better Font Awesome

    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: http://api.jsdelivr.com/v1/jsdelivr/libraries/fontawesome/?fields=versions,lastversion)

    Remote CSS Error
    The attempt to fetch the remote Font Awesome stylesheet failed with the following error: http_request_failed: cURL error 28: Connection timed out after 10001 milliseconds (URL: //cdn.jsdelivr.net/fontawesome/4.7.0/css/font-awesome.min.css)
    The embedded fallback Font Awesome will be used instead (version: 4.7.0).

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

    Solution
    This may be the result of a temporary server or connectivity issue which will resolve shortly. However if the problem persists please file a support ticket on the plugin forum, citing the errors listed above.
    ”

    But when I check those resources, I see they aren’t timing out, but redirecting to the https versions. Does the plugin need a response header status code check added so it can honor/follow (at least some safe-ish) redirects? it looks like it just ignores it for now and tries/waits for a 500 response it never gets…

Viewing 2 replies - 1 through 2 (of 2 total)
  • toolsavvy

    (@toolsavvy)

    5 years, 3 months ago

    You are getting this error because your web server is blocking outgoing connections to Better Font Awesome’s API IP address on apl.jsDelivr, which is 23.111.8.152.
    https://viewdns.info/reverseip/?host=api.jsdelivr.com&t=1

    I just spent an hour trying to figure this out, which is an abomination!!!!

    You have to allow outgoing connections to 23.111.8.152 in your web hosting control panel if your host allows that function. If not, you have to put in a ticket to your host’s support desk and ask them to unblock/allow outgoing connections to 23.111.8.152 because of a wordpress plugin you use.

    Theme and plugin developers need to start including outgoing connections information in their plugins pages and documentation be it can take a long time to figure out which blocked outgoing connection is for their theme/plugin. And if you don’t have access to that info, you have no idea what the problem is, like in your case.

    Wordpress needs to start requiring this information for any developers that want to upload themes/plugins to their repository!

    • This reply was modified 5 years, 3 months ago by toolsavvy.
    • This reply was modified 5 years, 3 months ago by toolsavvy.
    Thread Starter rslater_illinois

    (@rslater_illinois)

    5 years, 3 months ago

    @toolsavvy – Thanks! That makes sense. I know there were some security issues recently that lead to a tightening up of outbound traffic, so this reads.

    To the plugin author(s)– Would you consider leveraging both a file caching system (for necessary external files and a timeout on the file retrieval (like 3-4 seconds max)? Also, could you hook it to something that is end-user display triggered only? This currently appears to be hooked now in a way that when it is waiting the (I assume) system default amount of time to give up on fetching the file(s), it hangs everything (both the end user view and the WP dashboard). Finally, it would be nice if the plugin had a status page that would note if it had encountered access error for external resources/statuses of fetching them right now (for troubleshooting). Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘jsDelivr API server failed’ is closed to new replies.