question

pfournier avatar image
pfournier asked pfournier commented

remote pay cloud failure

Hi,

We are trying to run the remote pay cloud master application and are experiencing an error. We have done the following:

  • setup an application in sandbox.dev.clover.com with a URL for https://localhost:8443
  • downloaded and started remote pay cloud master and run via mvn jetty:run
  • downloaded the Cloud Pay app on our C300 and started it
  • browsed to the Sale page
  • entered configuration option #2 and set app ID, URL and device serial number.

We receive the following error: { "name": "CloverError", "code": "communication error", "message": "Error getting device information", "cause": "status returned was not 200" }

And see the following configuration when we get back to the main page which matches our app ID, entered URL and device serial number: (I x'd out the last 5 of each ID) { "clientId": "BBGWXCH0xxxxx", "domain": "https://sandbox.dev.clover.com/", "deviceSerialId": "C030UQ538xxxxx" }

Our device does appear to be able to communicate properly as I ran a couple of test transactions with the device running as a POS and had successful test charges go through.

Please advise as to what else we need to do.

Thanks,

Pete

2 comments
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

hammer avatar image hammer ♦ commented ·

Is the certificate that is presented from https://localhost:8443 fully trusted in the browser?

0 Likes 0 ·
pfournier avatar image pfournier commented ·

In Chrome I just get back the communication failed as above. I did add the site as a trusted site in IE, but still not working. The certificate does show as expired and the browser just times out and my last attempt actually came back with the same error.

0 Likes 0 ·

1 Answer

hammer avatar image
hammer answered

I would guess that you need to generate a new certificate. The certificate in the cloud example application expired on 12 April 2016. There are directions on how to generate a certificate on the README for the repo. See the section reading - "To regenerate the certificate to use a server name other than 'localhost'...", but just generate the certificate for localhost. You will need to delete the existing "src/test/resources/jetty.keystore", because you will be replacing it.

10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community