Error 403 - Forbidden Error
Error with WooCommerce Connection in Webgility Online
What is 403 Forbidden Error?
The 403 Forbidden error is a well-known HTTP status code that indicates the online store server understands the request and is refusing to authorize it. When using Webgility Online and WooCommerce, this error is typically related to the permissions given to the Webgility Store Module, which is located in the backend of the store and may not have enough permissions.
Common Causes of 403 Forbidden Error:
1). Incorrect File or Directory Permissions:
Proper permissions for files and directories are necessary for WooCommerce to work properly. If the permissions are incorrect, it may result in a 403 error.
2). Security Plugins or Firewall Restrictions:
The security plugins or server firewalls may be too strict, causing them to block valid requests to your WooCommerce website.
3). Incorrect Server Configuration:
Improperly configured servers, such as incorrect mod_security settings or strict server regulations, may lead to a 403 error.
4). Plugin Conflicts:
The 403 Forbidden error may occur if incompatible or incorrectly configured plugins clash with WooCommerce.
Step-by-Step Guide to Fix Error:
Updating the Webgility Store Module
1). Confirm the Current Version
Log In: Access your Webgility portal at portal.webgility.com.
Find Module URL: Navigate to Settings> Connections> WooCommerce. Click on Edit for your store.
Check URL: In the Webgility Store Module Address field, copy the URL.
Verify Version: Paste the URL into a web browser. The current version of the Webgility Store Module will be displayed.
2. Download the Latest Version
Access Downloads: In your Webgility portal, go to Home> Downloads> Modules.
Select Store Type: Choose WooCommerce.
Download: Locate and download the latest version of the Webgility Store Module.
Compare Versions: Check the version number against your current installed version.
3. Upgrade the Module
Deactivate Current Module:
Log in to your WooCommerce admin panel.
Go to Plugins> Webgility.
Click Deactivate and then Delete the existing Webgility Store Module.
Install New Version: Download the newest Webgility Store Module from your Webgility Portal account. Follow the instructions mentioned in this article How to Connect Webgility Online with WooCommerce.
4. Handle Custom Versions
Identify Custom Version: If your module version ends with a "C" or "I" when you check the module URL, it indicates a custom version.
Consult Support: Do not upgrade directly. Contact Webgility Support for guidance on how to proceed.
This structured approach ensures you keep your Webgility Store Module up-to-date and handle any custom versions properly.
Check File and Directory Permissions: Use an FTP client to verify and correct file and directory permissions.
Directories: 755
Files: 644
Ensure that the "wp-content" directory and its subdirectories are writable. "wp-content" is the directory location where the Webgility Store Module usually gets installed.
Manage Security Plugins: You can either disable or make an exception for the Webgility Store Module and its files in the additional security.
By following these steps, you should be able to identify and resolve the 403 Forbidden error in your WooCommerce store. If the problem continues, consider seeking assistance from your developer or a WooCommerce expert.
If you have any questions or need more help, please contact our support team.
Chat now.