PayPal (7) couldn't connect to host

Thanks Doc,
Have checked IPN and looks fine...

IPNCHECK.PHP - Version 1.3.9

CURL RESPONSE RECEIVED - Communications OKAYIPN TESTING - Response Received via CURL -- COMMUNICATIONS OKAY

IPN TESTING - Confirmation/Validation response with fsockopen(): FSOCKOPEN() RESPONSE RECEIVED - Communications OKAY
Default method likely to be used for communications is: CURL, with the fallback method being FSOCKOPEN if possible.Script finished.

Have checked AT&T network and looks fine...

command: traceroute https://www.toysahoy.com.au
connected via: route-server.ip.att.net
current datetime: Fri 23rd Aug, 2013 08:38 UTC
traceroute to toysahoy.com.au (203.170.87.225), 30 hops max, 40 byte packets

Not getting anywhere with Crazy Domains. they just tried to tell me that their server doesn't support Ecommerce unless it's Eshop although i reminded them that it was them that reccomended Zencart to me and that it has been working fine for 2 years.

Last good order received was on the 12th, first failure was on the 16th. I just launced another site with them which seems to be working fine.

Can someone please perform another check on this.

Mthirty5:

Have checked AT&T network and looks fine...

command: traceroute www.toysahoy.com.au
connected via: route-server.ip.att.net
current datetime: Fri 23rd Aug, 2013 08:38 UTC
traceroute to toysahoy.com.au (203.170.87.225), 30 hops max, 40 byte packets

This is actually a failed result. However, I had different results. also a failure.

**command: ** traceroute https://www.toysahoy.com.au
**connected via: ** route-server.ip.att.net
**current datetime: **Fri 23rd Aug, 2013 10:43 UTC

traceroute https://www.toysahoy.com.au traceroute to toysahoy.com.au (203.170.87.225), 30 hops max, 40 byte packets 1 gateway.cbbtier3.att.net (12.0.1.202) 2.597 ms 2.089 ms 2.751 ms 2 n54ny401me3-cbbtier3 (12.89.5.13) 2.795 ms 2.624 ms 3.248 ms 3 cr2.n54ny.ip.att.net (12.122.115.74) 6.455 ms 5.052 ms 3.869 ms 4 gar9.n54ny.ip.att.net (12.122.115.89) 5.026 ms 5.565 ms 4.146 ms 5 ae-15.r05.nycmny01.us.bb.gin.ntt.net (129.250.9.205) 3.529 ms 3.842 ms 3.575 ms 6 ae-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.68) 3.254 ms 3.528 ms 3.430 ms MPLS Label=302128 CoS=0 TTL=1 S=1 7 ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 13.213 ms 9.821 ms 8.916 ms MPLS Label=744387 CoS=0 TTL=1 S=1 8 ae-2.r21.lsanca03.us.bb.gin.ntt.net (129.250.3.55) 76.040 ms 73.744 ms 70.442 ms MPLS Label=302705 CoS=0 TTL=1 S=1 9 xe-0-0-0.r02.lsanca03.us.bb.gin.ntt.net (129.250.2.190) 75.772 ms 69.572 ms 101.583 ms MPLS Label=425745 CoS=0 TTL=1 S=1 10 as-1.r05.sydnau01.au.bb.gin.ntt.net (129.250.3.19) 207.592 ms--------------------------------------------

The problem seems to be somewhere between "ntt.net" and your host.

I've not heard of 'ntt' before.... I've no time to research ATM, but I can't help to wonder if this is a subsidary of AT&T?

Hopefully someone with more insight will make a little more of this than I can at the moment.

Cheers
Rod

Mthirty5:

Not getting anywhere with Crazy Domains.

I think I've identified the problem. (Actually I'm sure of it). It is almost certainly a CD configuration issue related to their SSL.

Wife is screaming at me to go to bed so I'm keeping this short. Here is what I've discovered. I'll leave it for someone else to 'interpret' what is going on here.

If they don't, just post a copy of the following outputs to the Crazy Domains tech team. Ask them just one question, namely WTF?

root@sue:~# dig -tany toysahoy.com.au
;; ANSWER SECTION:
toysahoy.com.au. 3203 IN TXT "Zone hosted on** cpanel13.per.syra.net.au**"
toysahoy.com.au. 7992 IN SOA ns4.syra.net.au. admin.syra.com.au. 2011090800 86400 7200 3600000 86400
toysahoy.com.au. 7992 IN MX 0 toysahoy.com.au.
toysahoy.com.au. 7900 IN A 203.170.87.225

root@sue:~# dig -tany cpanel13.per.syra.net.au
;; ANSWER SECTION:
cpanel13.per.syra.net.au. 2844 IN A 203.170.85.163

*note. different IP address even though the text record suggest this is where you are hosted.

root@sue:~# host 203.170.85.163
163.85.170.203.in-addr.arpa domain name pointer cpanel13.per.syra.net.au. ; // This is where your site should be.

root@sue:~# host 203.170.87.255 ;// This is where your site currently is.
255.87.170.203.in-addr.arpa domain name pointer** cp13-ssl-bcast.syra.net.au.** ;// This appears to be their SSL server???

Cheers
Rod

Thanks for your help on this Rod. I've advised Crazy Domains and am awaiting there response. With the lack of support from them, I'm considering changing hosts anyway now.

Mthirty5:

I've advised Crazy Domains and am awaiting there response. With the lack of support from them, I'm considering changing hosts anyway now.

Although Crazy Domains are far from the top of my list of good hosts, they do only charge $2.00p/m for their hosting, so a lack of support isn't entirely unexpected.

Having said that, cost isn't a good indicator of good support either. I get better support from our $5.00p/m host than I do from our $60p/m host. We use the hosts for different purposes though, and the cost difference is justified by what we can/can't do with each of them.

A good host is hard to find, and many hosts that start out good often end up going downhill over the years :(

Our sites are actually spread across no less than six different hosts and we are constantly migrating from those that have 'dropped the ball' to newer/better/faster/cheaper hosts according to market trends. It's been a long time since we've been 'emotionally attached' to any given host.

Cheers
Rod

Crazy Domains didn't understand your identified error and have now asked me to try https://api-3t.paypal.com/ as my hostname. I'm not sure how i'm supposed to do this.

FYI, i copied my entire website to another web host and paypal worked fine.

Mthirty5:

Crazy Domains didn't understand your identified error and have now asked me to try https://api-3t.paypal.com/ as my hostname. I'm not sure how i'm supposed to do this.Zen Cart already does that.

Mthirty5:

FYI, i copied my entire website to another web host and paypal worked fine.I think you've already identified what you need to do then.

Hi All

I've successfully run a zencart site for a few months now but have now suddenly started getting the (7) error overnight. No changes have been made anywhere (as far as I know)....

curltester results -

7 couldn't connect to host
Array
(
[url] => "http://www.zen-cart.com/testcurl.php"
[content_type] =>
[http_code] => 0
[header_size] => 0
[request_size] => 0
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.000314
[namelookup_time] => 2.6E-5
[connect_time] => 0
[pretransfer_time] => 0
[size_upload] => 0
[size_download] => 0
[speed_download] => 0
[speed_upload] => 0
[download_content_length] => -1
[upload_content_length] => -1
[starttransfer_time] => 0
[redirect_time] => 0
[certinfo] => Array
(
)

[primary_ip] => 192.168.241.146
[redirect_url] => 

)

ipncheck -

IPNCHECK.PHP - Version 1.3.9

CURL ERROR: Attempted connection on: https://www.paypal.com/cgi-bin/webscr

(7) couldn't connect to host

Trying direct HTTP on port 80 instead ...

CURL ERROR: Attempted alternate connection on: http://www.paypal.com/cgi-bin/webscr

(7) couldn't connect to host

ABORTING CURL METHOD ...

FAILED

IPN TESTING - Confirmation/Validation response with fsockopen(): FSOCKOPEN() RESPONSE RECEIVED - Communications OKAY

Default method likely to be used for communications is: FSOCKOPEN, with the fallback method being CURL if possible.

Script finished.

an advice on interpreting results appreciated!

royaldave:

I've successfully run a zencart site for a few months now but have now suddenly started getting the (7) error overnight. No changes have been made anywhere (as far as I know)....

curltester results -

7 couldn't connect to host
[url] => "http://www.zen-cart.com/testcurl.php"

CURL ERROR: Attempted connection on: https://www.paypal.com/cgi-bin/webscr
(7) couldn't connect to host
Your server's CURL communications (outbound on ports 80 (http) and 443(https) ) are broken.
It's like your hosting company closed the firewall to stop all normal outbound communication.
Only your host can fix the issue.

DrByte:

Your server's CURL communications (outbound on ports 80 (http) and 443(https) ) are broken.
It's like your hosting company closed the firewall to stop all normal outbound communication.
Only your host can fix the issue.

Thanks for the response.

Payments are working again without me doing anything - hopefully this was a one-off - will have to keep an eye on it.