How can we help you?

How to deal with the IP blocking

Store migration with Cart2Cart consists of transferring data entities between the Source and Target platforms’ databases. Since our automated tool does not interact with these carts directly, a Connection Bridge is necessary to establish the connection between the databases.

A Connection Bridge is a file that links to the database and requests to delete, import, or retrieve data. In other words, Cart2Cart interacts with its Bridges and, therefore, makes them follow a set of instructions that affect the data. Thus, these Bridges have to be active during the whole store migration process.

To execute a bridge request (i.e., instructions to work with data), we use regular HTTP queries. The request ports depend on the type of protocol (HTTP or HTTPS) the source and target carts use. These are ports 80 and 443, respectively. Most requests use an HTTP POST request, and it is more secure than the GET request. Moreover, it can send and receive a larger volume of data.

The Bridge usage frequency depends on how long it takes to establish the Internet connection with the store and the complexity of the request (the more complicated it is, the longer the automated tool waits for a response, and processes the result).

The most common reason for hosting blocking is the number of requests per time unit from a single PC (IP address). Also, the blocking may occur due to the HTTP POST method usage (since the browser applies the GET method even for a standard web surfing or cart’s web-page navigation). Sometimes the hosting may be blocked because all the requests are being sent to the same address - i.e., the Bridge (bridge2cart/bridge.php).

How Cart2Cart deals with hosting blocking:

• Make requests from a different IP address.

How to unblock the migration requests:

• Allow more requests to the server per time unit.
• Make sure that the store is accessible in all the countries (check, if it doesn’t block any IP addresses).
• Permit additional inbound/outbound Internet traffic.
• Remove all the restrictions on the database requests’ execution and the number of connections to it.