Unable to acquire | CyberSEO Pro | Support Forum

The problem you’re facing involves several potential issues related to networking, server configuration, and possibly security policies that may be preventing the plugin on Hosting B from accessing data on Hosting A. Here’s a step-by-step approach to troubleshooting and possibly solving the problem:

Start by checking the error logs on both Server A and Server B. This may give you more detailed information about what’s going wrong, particularly regarding connection timeouts and memory issues.

Check the network configuration and make sure that the firewall settings on both servers are configured to allow connections on the required ports (typically port 443 for HTTPS). Confirm that there are no IP address blocks or restrictions that might affect connections between the two servers. It appears that Server B’s IP is being blocked by Server A, so make sure that the new routing and IP address changes have been properly updated and propagated.

Check memory and resources and memory usage on Server A, especially if the server is experiencing low memory issues. This could be affecting the server’s ability to handle incoming requests. Consider increasing the memory limit settings in PHP and other relevant configuration settings if you’re consistently hitting memory limits.

Check your cURL and PHP configuration. On server B, where the CyberSEO Pro plugin is hosted, make sure that PHP’s cURL extension is configured correctly and has sufficient timeout settings to wait for responses from server A. You may want to increase the cURL timeout setting in your PHP configuration, especially if the connection between the two servers is slow or unstable.

Test the direct connection. From server B, try to manually access the URL Login to see this link using a tool like cURL directly from the command line. This can help confirm if the problem is specific to the plugin or a more general server-to-server connection issue.

Contact hosting support again. With specific error logs and findings from the steps above, contact the hosting support teams again. Provide them with detailed information to help them better understand the issue.

If direct server-to-server communication continues to be unreliable, consider setting up an intermediate storage solution where Server A pushes data to and Server B fetches it from. This can be as simple as an AWS S3 bucket or other web service that both can reliably access.

This approach should help you narrow down the cause of the problem and find a solution to get your plugin working again. If these steps don’t solve the problem, you may need to contact a network or server specialist for more in-depth troubleshooting.

P.S. It’s also possible that the feed owner on server A has blocked the IP address of server B. Security systems often automatically block IPs when they detect suspicious activity, such as too many requests in a short period of time that could be seen as a DDoS attack, or the feed owner doesn’t want it imported by third parties. You should contact Server A’s support team to verify this and discuss whether the block can be lifted. Additionally, if you have access to Server A’s settings, check the security and firewall settings to see if Server B’s IP is specifically blocked. Using a Login to see this link can help in this situation.