Title: Error proxying &#8211; timeout
Last modified: January 31, 2017

---

# Error proxying – timeout

 *  [vahost](https://wordpress.org/support/users/vahost/)
 * (@vahost)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/error-proxying-timeout/)
 * An error keeps popping up in my error_log file:
 * [31-Jan-2017 17:10:33 UTC] AdmiralAnalytics: Error proxying: {“code”:28,”str”:”
   Timeout was reached”,”type”:”curl”,”debug”:”* Resolving timed out after 3513 
   milliseconds\n* Closing connection 0\n”}

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Admiral](https://wordpress.org/support/users/getadmiral/)
 * (@getadmiral)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-8726593)
 * [@vahost](https://wordpress.org/support/users/vahost/), Would you be able to 
   provide us with your URL, we’re going to look into the issue and see what’s going
   on.
 * You can also email [Support@GetAdmiral.com](https://wordpress.org/support/topic/error-proxying-timeout/Support@GetAdmiral.com?output_format=md)
   or go to [http://www.GetAdmiral.com](http://www.GetAdmiral.com) and we can have
   a live support chat there.
 *  Thread Starter [vahost](https://wordpress.org/support/users/vahost/)
 * (@vahost)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-8726736)
 * Message sent to [support@getadmiral.com](https://wordpress.org/support/topic/error-proxying-timeout/support@getadmiral.com?output_format=md).
 *  Plugin Author [Admiral](https://wordpress.org/support/users/getadmiral/)
 * (@getadmiral)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-8727651)
 * [@vahost](https://wordpress.org/support/users/vahost/), we’re looking into it
   now. We’ll get back shortly. Thank you.
 *  [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/)
 * (@leopard-lady)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-9063585)
 * I’m finding similar entries in my error logs:
 * mod_fcgid: stderr: AdmiralAnalytics: Error proxying: {“code”:6,”str”:””,”type”:”
   curl”,”debug”:”* name lookup timed out\\n* Couldn’t resolve host ‘owlsr.us’\\
   n* Closing connection #0\\n”}
 * The errors go all the way back to February when I installed this plugin.
 * Any ideas on what is causing this please and how I should remedy the issue?
 * Thank you,
    LL
 *  [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/)
 * (@leopard-lady)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-9066988)
 * I ran debug and logged it for the past 20 hours. This is what is posted to the
   log several times – hopefully this gives you more insight to the error issue 
   I posted above last night:
 * PHP Notice: Use of undefined constant CURL_SSLVERSION_TLSv1 – assumed ‘CURL_SSLVERSION_TLSv1’
   in /var/www/vhosts/example.com/httpdocs/wp-content/plugins/admiral-adblock-suite/
   AdmiralAdBlockAnalytics.php on line 286
 * EDITED TO ADD:
    Just noticed one instance of this posted on the debug log: AdmiralAnalytics:
   Error proxying: {“code”:6,”str”:””,”type”:”curl”,”debug”:”* name lookup timed
   out\n* Couldn’t resolve host ‘owlsr.us’\n* Closing connection #0\n”}
 * It is same as what is posted repeatedly in my server error logs.
 * Thank you,
    LL
    -  This reply was modified 9 years, 1 month ago by [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/).
    -  This reply was modified 9 years, 1 month ago by [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/).
    -  This reply was modified 9 years, 1 month ago by [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/).
 *  [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/)
 * (@leopard-lady)
 * [9 years ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-9125645)
 * Another issue with this plugin is that it is constantly making calls to the /
   wp-includes/js/ folder looking for non-existent randomly named php files. Each
   time this happens it throws a 404, hangs the page load and fires a status code
   500 internal server error.
 * This plugin is groovy in concept. I really would like to track the volume of 
   visitors running ad blockers . . . but I’ve just deleted your plugin. It causes
   too many errors on the server and severely hangs up pageload. Top that with no
   response to support posts for over 2 weeks and it’s a no-go.
 * LL

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Error proxying – timeout’ is closed to new replies.

 * ![](https://ps.w.org/admiral-adblock-suite/assets/icon-256x256.png?rev=1430494)
 * [Admiral Adblock Analytics](https://wordpress.org/plugins/admiral-adblock-suite/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/admiral-adblock-suite/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/admiral-adblock-suite/)
 * [Active Topics](https://wordpress.org/support/plugin/admiral-adblock-suite/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/admiral-adblock-suite/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/admiral-adblock-suite/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Leopard-Lady](https://wordpress.org/support/users/leopard-lady/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/error-proxying-timeout/#post-9125645)
 * Status: not resolved