question

Have you tried manually starting Cloud Pay Display? The mechanism that auto starts CPD may be having an issue in sandbox.

It works when I start CPD manually, but I have to prove that the code works before implement it in our app.

Message: {"method":"REMOTE_ERROR","version":0,"errorDetail":"We could not start Cloud Pay Display: A non-200 response (404) was received from the Clover server. Please manually start Cloud Pay Display on your Clover device.","errorMessage":"Unable to start Cloud Pay Display. Please manually start Cloud Pay Display and then attempt to establish a connection.","errorCode":"NotConnected"}

I'm having a similar problem on the Duo... will it work once out of the sandbox?

{"message":"An error has occurred and we could not establish a connection to your Clover device: C055UG35232135 within the timeout period of 15 second(s). Please manually start Cloud Pay Display on your Clover device and try again.","requestId":"26c66756-27536","requestType":"DISPLAY_MESSAGE","type":"TIMEOUT"}

I have no way to manually start Cloud Pay Display on the Duo small-screen... it has no interface.

I did sideload Cloud Pay Display on the Duo big-screen, and it works if manually started! ...but obviously I want it on the small-screen, not the big-screen. Is the Duo just not compatible? ...or will it work auto-launching Cloud Pay Display instead of Pay Display once I am out of the Sandbox?

If you're following the Remote Pay Cloud tutorial and encountering issues where the CPD (Clover Payment Device) does not automatically show up, despite a successful connection, it can be frustrating. Here’s a structured approach to diagnose and resolve the issue based on the details you've provided:

Troubleshooting Steps

1. Verify Network Configuration

   • Network Connection: Ensure that your development kit and the device running the Clover Remote Pay Cloud are on the same network. Network issues or firewalls can sometimes block communication.
   • WebSocket Ports: Ensure that any firewalls or network security groups are configured to allow WebSocket connections on the necessary ports.

2. Check Dev Kit and Server Status

   • Dev Kit Connection: Verify that the dev kit is properly connected and powered on. Ensure that any setup or pairing processes required by the dev kit are complete.
   • Server Status: Check the status of Clover's Remote Pay Cloud service to ensure there are no ongoing outages or maintenance affecting the service.

3. Review WebSocket Errors

   • 503 Error Analysis: A 503 Service Unavailable error usually indicates that the server is temporarily unable to handle the request. This could be due to server-side issues or temporary network problems. If the error occurs consistently, it might be worth checking if there are known issues on Clover's status page or forums.
   • Error Logs: Review the console logs and any error messages in detail to gather more information on what might be causing the issue. Look for any specific error messages or stack traces that might indicate a problem.

4. Verify Tutorial Steps

   • Correct Steps: Double-check that you’ve followed each step of the tutorial correctly. Sometimes missing a configuration step can lead to issues with CPD display.
   • Sample Code: Ensure that the sample code or configuration provided in the tutorial is correctly implemented and that no steps have been skipped.

5. Test with Sample Code

   • Try Sample Code: Use any sample code provided in the tutorial or available in the Clover documentation to verify if the issue persists. This can help determine if the issue is with your specific implementation or a more general problem.

6. Check Console and Network Tab

   • Developer Tools: Open the browser's developer tools (usually accessible via F12 or right-click > Inspect) and check the Console and Network tabs for any errors or failed network requests. This can give you clues about what's going wrong.

7. Reboot Devices

   • Restart Devices: Sometimes, simply restarting your development kit and the device running the Clover Remote Pay Cloud can resolve connectivity issues.

8. Update and Compatibility

   • Software Updates: Ensure that you are using the latest versions of the development kit firmware, Clover SDK, and any other related software. Compatibility issues with older versions can sometimes cause unexpected problems.
   • www.njmcdirect.com
     
     
     
     

To troubleshoot the 503 error, make sure the websocket is initialized properly and the connection is stable. Check the server, make sure the network connection is stable and there are no firewall or proxy settings blocking the connection. Because if it is, even if you go to another page like playing geometry dash scratch, it will not work. Next, double check the CPD launch code to see if it is correct. There may be a small error or missing part in the tutorial that is causing the CPD to not launch.