Error: The Remote Server has Returned Error 400

Error: The Remote Server has Returned Error 400

David Pond avatar
Written by David Pond
Updated over a week ago

Error: The Remote Server has Returned Error 400

When attempting to test your store connection in Webgility, encountering error code 400 from the remote server can be a roadblock. This issue is often caused by security or firewall settings on the website server. However, there's no need to worry as we have a step-by-step guide to help you resolve this problem and get your Webgility integration up and running smoothly.

Error Description:

Error 400 is a common HTTP status code that indicates a bad request. In the context of Webgility, this error is likely a result of security or firewall measures preventing proper communication between your website and Webgility.

Potential Causes:

Security and Firewall Settings: Enabled security features or firewalls on the website server can hinder the necessary connections, leading to error 400 during the store connection test.

Resolution Steps:

Verify Hosting Provider's Security Settings:

1). If your website is hosted by a provider, it's essential to check if they have any security measures in place that might be interfering with Webgility's communication. If so, you'll need to add an exception for Webgility on the Website security settings (firewall).

2). Whitelist the Required IP Addresses: To enable seamless communication between your website and Webgility, you must whitelist the following IP addresses on your server:

By whitelisting these IPs, you grant Webgility the necessary access to your server, preventing error 400.

Implementing changes related to server security and IP whitelisting requires technical expertise. To ensure proper execution, involve your website's web developer. They will have the knowledge and experience to make the necessary adjustments accurately.

If the issue still persists then please contact the Webgility Suppor team with store FTP and admin login details so we can investigate with our developers.

Did this answer your question?