403 Forbidden Error - Magento
This article helps Webgility Online users resolve the 403 Forbidden error that may occur in Magento v1 when connecting with Webgility Online. The error typically arises due to server restrictions such as incorrect permissions, misconfigured .htaccess files, missing index files, or firewall/security rules. It indicates that the server understood the request but denied access. The guide provides troubleshooting steps to reauthorize the Magento sales channel, verify access credentials, and whitelist Webgility IP addresses to restore proper connectivity.
Overview:
A 403 Forbidden error occurs when a server understands a request but refuses to fulfill it. In Webgility, this error is most common with PHP-based shopping carts such as Magento. It is typically caused by incorrect file or directory permissions, a misconfigured .htaccess, missing index files, or security/firewall restrictions. It indicates the request was understood but denied.
Steps to fix:
1. Verify the Sales Channel Connection
-
Go to Connections → Magento → Reauthorize

Step 2: Confirm the Sales Channel URL and Provide Webgility Extension folder Access
-
Update Store Module URL, Store Admin Username and Password → Next → Finish to reauthorize the Sales Channel.

3. If the 403 Error Persists
-
Ensure the required Webgility IPs are whitelisted on the store server hosting your Magento channel.
Add the following Webgility IP addresses to your server's allowlist:
54.69.99.71
183.182.84.170
111.118.255.21
- Permissions for the Webgility Extension or folder must allow full read/write permissions (e.g., chmod 755 or 777 on Linux-based servers). Incorrect permissions will cause the server to deny Webgility's requests.
-
Once updated, test the connection again in Webgility Online:
-
Navigate to Connections → Magento → Reauthorize → Next → Update Store Module URL, Store Admin Username and Password → Next → Finish.
-