Skip to main content

Server Communication Errors

Updated

Overview

This article will provide a high level overview of troubleshooting steps for Server Communication Errors. Server Communication Errors may occur within the SDK when the client is unable to communicate with the server. This error generally occurs due to local network connectivity issues or due to the networks firewall and settings blocking communication.

Server communication errors can be attributed to a number of factors:

  • Network layer issues
  • DNS resolution issues
  • Operating system and other software issues (e.g. Antivirus/Firewall)
  • Certificate checking/revocation issues

Due to the nature of these errors it is recommend prior to reaching out to support that any available networking teams review any restrictions set by the network's firewall or settings.

 

Test Connectivity 

We normally recommend those who are seeing issues with Server Communication Errors to test their general network connectivity to the platform.

In order to do this you will simply need to open the following URLs within a web browser:

Live Platform Links:
https://tms.cardeasexml.com/pingdom
https://live.cardeasexml.com/pingdom

Test Platform Links:
https://testtms.cardeasexml.com/pingdom
https://test.cardeasexml.com/pingdom

When entering these URLs into the browser a successful connection will show pool_up without any certificate error. 

 

Allow All SDK IP Addresses

If you are receiving any Server Communication errors, the first recommended step is to verify if all of the Payment Device SDK IPs have been allowed within the network. Allowing the IPs is also recommended when an estates is utilizing restrictive networks. This is normally done through the location's network settings/firewall. We recommend reviewing these rules to confirm if these IPs have been added to the network settings.

You may find the full list of the Payment Device SDK's IP addresses within the "Firewall Configuration" section of the Payment Device SDK documentation.