Skip to main content
All CollectionsWebgility DesktopAdvice & troubleshootingConnection Related
The Input is not a valid Bas-64 string as it contains a non-base 64 character, more than two padding characters, or an illegible character among the padding characters
The Input is not a valid Bas-64 string as it contains a non-base 64 character, more than two padding characters, or an illegible character among the padding characters

The Input is not a valid Bas-64 string

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

The Input is not a valid Bas-64 string as it contains a non-base 64 character, more than two padding characters, or an illegible character among the padding characters

This error is caused when the input value does not strictly follow the base64 encoding rules. The most common reasons for this error are invalid characters, more than two padding characters, or illegible characters among the padding characters.

Error Message:

The Input is not a valid Bas-64 string as it contains a non-base 64 character, more than two padding characters, or an illegible character among the padding characters.

Troubleshooting

  1. Check your sales channel credentials, this includes login URL, username, password, and API token, for the specified sales channel. To check the same, please follow the below steps:

    1. Go to Integrations> Stores> Manage and click Edit Connection in the sales channel that is experiencing the connection issue.

    2. Continue until you are on the store settings page and confirm the accuracy of the username and password, then click Connect to Store.

    3. Once connected successfully, continue through the connection wizard, go to the configuration screen, and then attempt to update the sales channel data.

  2. Add exemptions to your antivirus software. Add C:\Webgility to the exemption list and restart the Webgility software.

  3. From the store connection screen in Webgility, in the store module URL you can try using “https”or “http”.

  4. You may also try to add or remove “www” from the store module URL

  5. Make sure the server is not blocking the connection, check and ensure the below-mentioned IP addresses are whitelisted:

    1. 183.182.84.170

    2. 111.118.255.21

    3. 54.69.99.71

If the issue persists, please feel free to contact us.

Did this answer your question?