Invalid Length for a Base-64 Char Array or String
When using the Webgility Extension to manage cart connections, you might encounter Base64 errors, especially when downloading orders or testing the store connection.
Common Causes of Base64 Errors:
1). Inconsistent URL Protocol (HTTP/HTTPS):
Base64 errors can occur if the Webgility Extension URL uses a different protocol (HTTP or HTTPS) than the one configured for your website.
2). Incorrect or Outdated Webgility Extension URL:
Using an outdated or incorrect Webgility Extension URL can trigger these errors. It’s essential to ensure that the URL is both accurate and up-to-date for proper integration.
Troubleshooting Steps:
1). Verify the URL Protocol:
Check the Webgility Extension URL's protocol (HTTP or HTTPS) in the Webgility Integration settings.
Ensure it matches your website's protocol.
Go to Settings> Connection> Edit> Update Credentials. Try switching between HTTP and HTTPS, then test the connection.
2). Confirm Webgility Extension URL:
Validate the Webgility Extension URL by accessing the latest URL from the store directly.
Update it in the Webgility Integration settings.
3). Update Webgility Extension:
Make sure your Webgility Extension is running the latest version.
Download and install the most recent version from Webgility's Portal.
If you need help, contact your developer.
If the Base64 error continues despite following the steps above, please contact the Webgility support team. We will help investigate the ‘warn logs’ to pinpoint the exact error cause and involve our developer in further investigation.
If the issue continues, please reach out to Webgility Support for more help.