Connection refused (-111)

Connection refused (-111)

11 posts / 0 new
Last post
Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0
Connection refused (-111)

Hi,

We are developing a website for a customer that has an Acquia Subscription. We tried to enable the subscription, but get an error saying:
"There is an error communicating with the Acquia Network at this time. Please check your identifier and key and try again."

The log states (removed the actual id and stuff):
"Connection refused (-111): https://rpc.acquia.com/xmlrpc.php - acquia.agent.validate -
Array
(
[authenticator] => Array
(
[identifier] =>
[time] => 1281002041
[hash] =>
[nonce] =>
)

[host] =>
[body] => Array
(
)

)"

We've tried enabling and disabling the Enhanced SSL Security and checked all the settings in the Acquia subscription. The server is capable of sending http requests to the acquia.com domain (verified with a drupal_http_request() call).

Any help is much appreciated...

Kind regards,
Martijn

Status: 
Resolved
mhaag's picture
michael.haag
Points: 0

Martijn, does the customer have a reverse proxy in place?

Also, could you pls ask the customer open a ticket using their acquia.com subscription (or could you do it on their behalf)? It is not necessary to have drupal talking to the Acquia Network in order to open tickets and get support.

regards, -m

Michael Haag
Customer Advocate/Quality Evangelist
Tech Support

regards, -m

Michael Haag
Customer Advocate/Quality Evangelist
Tech Support

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

Sorry: double post.

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

Hi Michael,

Thanks for your quick response. I don't know if the hosting partner has a reverse proxy. I'll have to ask them. Why is that important and what could be the problem/solution if they do have one in place?

My customer has a Basic subscription that does not allow the registration of tickets (that was my first attempt to get support). That's why I openend a forum topic (because no other forum topic covered my problem).

Kind regards,
Martijn Vermeulen

mhaag's picture
michael.haag
Points: 0

Martijn, acquia_agent uses acquia_agent_http_request() for communication which
has no proxy support. I have seen symptoms like yours when the web server is behind a proxy. If there is a proxy involved, then pls try this patch:

https://acquia.com/files/acquia_agent_streams.inc_.patch

regards, -m

regards, -m

Michael Haag
Customer Advocate/Quality Evangelist
Tech Support

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

Hi Michael,

I have no response from the hosting provider yet, but I thought I'd try the patch anyway. Unfortunately in the patch the function "is_in_no_proxy_list()" is called which results in an "undefined function" error.

Regards,
Martijn

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

The hosting provider responded and they do have a reverse proxy in place for outgoing http requests.

I have not made any progress with the is_in_no_proxy_list() function problem that is in the patch you recommended.

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

I've tested if the unpatched version of acquia_agent_http_request() can perform a http request, despite the reverse proxy being in place. The result was positive (I got a clean response with a result body and all).

So: where is the "connection refused (-111)" coming form?

Is the Acquia agent using some kind of strange context, ports or protocols?

renny1's picture
renny1
Points: 0

I was having this issue too as my development site is behind a proxy and the patch that Michael provided fixed the problem. Thanks Michael.

For the time being I have hard coded the proxy_not_required variable to FALSE. I would say for development purposes this should be ok.

//$proxy_not_required = is_in_no_proxy_list($uri['host']);
$proxy_not_required = "FALSE";

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

Wow, why didn't I think of that... Anyway, tried it and now we are connected to the Acquia network. However, the Acquia Search now gets the -111 refused error. I'm suspecting that the proxy does not allow connection to search.acquia.com and only to www.acquia.com, so I've sent an e-mail to the hostin provider (again).

Like Renny says: manually setting the $proxy_not_required is fine for development, but not for a production site.

Any idea why is_in_no_proxy_list() results in an undefined function error?

Martijn.Vermeulen's picture
martijn.vermeulen
Points: 0

The hosting provider solved the entire proxy/firewall problem so now the unpatched code works. The subscription is active and the statuspage says that the Acquia Search has been contacted.

However, when the cron runs I get log messages saying:

"0" Status: Request failed: Connection refused. Connection refused
request ID: 4c73de740143b
in apachesolr_cron

and a message saying that indexing failed.

The hosting provider has checked the requests at network level, but only sees a ping request that returns a HTTP 200 "OK" and no other requests.

What could be wrong now?