Support

 Trying to a test restore for the first time.

in Step 1
- import from Amazon S3
- after cutting and pasting access id and key that worked for the backup,
- Connect to Amazon S3

no response?

After reading a support ticket, tried:
- un remarking the curl extension
- turning the firewall OFF
- deactivating and reactivating the SSL for the domain

No luck, can not get to Step 2 - selecting the S3 bucket from the drop down?

Guessing I am missing a step? or server config?

used the IAM policy simulator to confirm that ListBuckets action was allowed for the user credentials.

I went back to the Kickstart Pro 3.8.1 download and noticed that it was "Compatible with JPA, JPS & ZIP archives, PHP 5.3.4 and later."

Upgraded to PhP5.3 on the server.

Retried Connect to Amazon S3 and got a new error:
S3::listBuckets(): [6] Could not resolve host: s3.amazonaws.com (Could not contact DNS servers)

Researching that error now.

FYI, from server:

traceroute s3.amazonaws.com
traceroute: unknown host s3.amazonaws.com

[root@*********]# dig s3.amazonaws.com

; <<>> DiG 9.8.5-P2-RedHat-9.8.5-3.P2 <<>> s3.amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 39298
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;s3.amazonaws.com. IN A

;; Query time: 0 msec
;; SERVER: 199.238.136.78#53(199.238.136.78)
;; WHEN: Wed Jun 11 10:56:59 MDT 2014
;; MSG SIZE rcvd: 34


From mxtoolbox.com:
trace:s3.amazonaws.com

trace


HopCount IP Address HostName
1 208.123.79.34 net208-123-79-34.static-customer.corenap.com
2 198.252.182.180 aus-core-10-v12.corenap.com
3 198.252.182.149 aus-core-11-v11.corenap.com
4 64.125.32.201 xe-8-1-1.er2.dfw2.us.above.net
5 64.125.20.233 ae7.cr2.dfw2.us.above.net
6 64.125.21.62 ae2.cr2.iah1.us.us.above.net
7 64.125.21.53 ae14.cr2.dca2.us.above.net
8 64.125.21.58 ae4.er2.iad10.us.above.net
9 64.125.29.77 xe-5-1-0.cr2.dca2.us.above.net
10 * * * * * *
11 * * * * * *
12 * * * * * *
13 * * * * * *
14 * * * * * *
15 * * * * * *

Nicholas,

Thanks for the support on this issue.

We were able to complete a test restore on a different server.

We also were able to get our hosting provider to resolve the DNS issue on which we we were initially testing the restore:

"There was caching issue. We restarted the DNS services on the root of the server and now it is resolving fine..."

Thank you for the prompt, professional and informative support.