Introduction
When setting up the connector for your web store, you might encounter some common issues that could prevent it from working properly. Don't worry; we're here to help you troubleshoot and get things running smoothly! Below, we've outlined some easy-to-follow steps to resolve the most common connector installation problems.
Problem 1: 406 Not Acceptable
The "406 Not Acceptable" error occurs when a request sent to your source store server is blocked by the server. It often happens due to server settings such as mod_security or limits on POST requests. Follow these steps to fix it:
1. Increase the POST request limit on your server. For example, set: post_max_size = 512M
2. Check server security settings, such as mod_security, to ensure they are not blocking the request.
For more detailed guidance, see: How to fix 406 error
Problem 2: 404 Not Found Error
If you're seeing a "404 Not Found" error when searching for the connector, likely, the connector wasn't installed in the right location. Follow these steps to fix it:
1. Make sure the connector is in the correct path: Your connector should be located at your_store.com/mp_connector/connector.php. Double-check the path to ensure it's correct.
Problem 3: 403 Forbidden Error
A 403 Forbidden error means the web server understood the request but refuses to allow access.
This usually happens because the server security configuration blocks execution of the connector script.
Below are the most common causes and how to resolve them.
Problem 1: Web Server Security Rules (Apache / Nginx)
Some hosting providers block execution of unknown or custom scripts for security reasons. In this case, the web server configuration denies access to PHP or executable files that are not explicitly allowed.
To allow the connector to work, you must add an exception for the connector file.
Apache Web Server
You may find a .htaccess file in the root directory of your shop.
Step 1 — Open .htaccess
Open the file using any text editor.
Step 2 — Find blocking rule
Look for something similar to:
<FilesMatch ‘.(py|exe|php|PHP|Php|PHp|pHp|pHP|pHP7|PHP7|phP|PhP|php5|suspected)$’>
Order allow,deny
Deny from all
This rule blocks execution of PHP files.
Step 3 — Exclude connector.php
Modify the rule to exclude the connector file by adding a negative exception:
<FilesMatch ‘^(?!connector.php$).*.(py|exe|php|PHP|Php|PHp|pHp|pHP|pHP7|PHP7|phP|PhP|php5|suspected)$’>
Order allow,deny
Deny from all
This keeps server protection enabled while allowing the connector to run.
Nginx Web Server
Locate your Nginx site configuration file.
Depending on your hosting environment, it may be located in:
/etc/nginx/sites-enabled/
or inside your project/server root directory (Docker or managed hosting setups).
Step 1 — Find blocking rule
Look for rules similar to:
location ~ .php$ {
deny all;
}or:
location ~* .(php|exe|py)$ {
deny all;
}These rules prevent execution of PHP scripts.
Step 2 — Add connector exception
Add a more specific rule above the blocking rule:
location = /mp_connector/connector.php {
include fastcgi_params;
fastcgi_pass unix:/run/php/php-fpm.sock;
}Note: the fastcgi_pass value may differ depending on server configuration.
Step 3 — Reload Nginx
After saving changes, reload Nginx:
sudo systemctl reload nginx
Problem 2: Firewall Restrictions
A 403 error may also be caused by a firewall or security system blocking access to the connector.
This may include:
Hosting firewall
ModSecurity
Cloudflare or similar protection
Server security plugins
How to check
Temporarily disable the firewall (if you manage the server).
Try accessing the connector again.
If it works, whitelist the connector path:
mp_connector/connector.php
or allow your integration IP address.
Problem 3: File Permissions
Incorrect file permissions can also result in a 403 error.
Ensure the connector file exists and has readable permissions:
mp_connector/connector.php
Recommended permissions:
Files: 644
Folders: 755
On managed hosting platforms, make sure the web server user has permission to read the file.
Important Notes
Always create a backup before modifying server configuration files.
Some hosting providers restrict access to server configs. If you cannot edit them, contact your hosting support.
After making changes, clear server cache or CDN cache if enabled.
Our Migrationpro Support Team is here to help!
Feel free to contact us via email at [email protected] or use the Live Chat available in the bottom-right corner of the page!