PrestaShop Multistore OAuth Errors: Solving ps_accounts Redirect URI Mismatches
Navigating PrestaShop Multistore OAuth Challenges: A Deep Dive into ps_accounts Redirect URI Errors
In the dynamic and often complex world of e-commerce, PrestaShop's multistore feature offers unparalleled flexibility for merchants managing multiple brands or regions from a single installation. However, this power comes with its own set of intricate challenges, particularly when integrating with external services like PrestaShop Account via OAuth. A common, yet perplexing, issue that can arise is the 'invalid_request' OAuth error, specifically related to the redirect_uri parameter within the ps_accounts module. This problem is exacerbated in a multistore environment, where one shop might function perfectly while another struggles to connect.
At Migrate My Shop, we frequently encounter scenarios where merchants, like the one described in a recent PrestaShop forum thread, face this exact hurdle. The original poster, dato_1234, detailed a frustrating situation with a PrestaShop 9.1.3 multistore setup. While 'Frazycars' operated flawlessly with PrestaShop Account, 'FoxLabStudios' consistently failed to complete its login, despite being verified and having its own distinct Cloud Shop ID and domain (https://www.foxlabstudios.pl/).
The invalid_request Conundrum: When One Store Works, and Another Doesn't
The core of dato_1234's problem lay in the OAuth process returning a stark error message: "Error: invalid_request. The 'redirect_uri' parameter does not match any of the OAuth 2.0 Client's pre-registered redirect urls." This message is a clear indicator that the URL PrestaShop is sending to the OAuth provider for callback doesn't align with what the provider expects. The initial troubleshooting steps taken by dato_1234 were thorough:
- Ensuring
ps_accountswas up to date. - Verifying 'FoxLabStudios' within the module.
- Confirming unique Cloud Shop IDs for each store.
- Clearing and resetting the
ps_accountsmodule. - Accessing the Back Office directly under the problematic domain.
- Confirming correct HTTPS detection.
Despite these efforts, 'FoxLabStudios' remained unsynchronized, pointing towards a deeper, more subtle configuration issue rather than a superficial module glitch.
Unpacking ps_accounts and OAuth: The Dynamic redirect_uri
The key to understanding and resolving this error lies in how the ps_accounts module interacts with the OAuth provider. As insightfully pointed out by Knowband Plugins in the forum, the redirect_uri isn't a static value manually entered somewhere. Instead, the ps_accounts module dynamically constructs this URI using each shop's specific domain settings via PrestaShop's internal Link::getAdminLink(..., $shopId) function. This means the problem isn't a 'broken client' or an incorrect hardcoded URL, but rather a 'domain mismatch' originating from the PrestaShop configuration itself.
The Root Cause: PrestaShop Multistore Domain Mismatch
The dynamic generation of the redirect_uri makes the 'Shop URL' configuration within PrestaShop's multistore settings critically important. Any discrepancy between the actual domain being used to access the Back Office and the domains registered in PrestaShop's database for that specific shop will lead to an OAuth failure. Common culprits include:
- Missing or Extra
www: If your shop URL ishttps://www.example.combut PrestaShop's configuration for that shop is set tohttps://example.com(without www), the redirect URI will mismatch. - Protocol Mismatch: Using
http://in the configuration when the site is accessed viahttps://(or vice-versa). - Stale SSL Domain: After migrating to SSL, the
SSL domainfield might not have been updated correctly or consistently. - Trailing Slashes: Inconsistent use of trailing slashes in the domain configuration.
These seemingly minor differences are enough to break the OAuth handshake, as the security protocol demands an exact match for the registered redirect URI.

Actionable Solutions: Fixing Your ps_accounts Multistore OAuth Error
Step 1: Meticulous Verification of Shop URLs
This is the most critical step. Navigate to your PrestaShop Back Office:
- Go to Advanced Parameters > Multistore.
- Click on the Edit button for the problematic shop (e.g., 'FoxLabStudios').
- Under the Shop URLs section, carefully examine each row. Ensure that the Domain and SSL Domain fields precisely match the actual domain you use to access that specific shop's Back Office, including the 'www' prefix if applicable, and the correct protocol (HTTPS).
- Pay attention to the Physical URI and Virtual URI as well, ensuring they are correct for your server setup.
For instance, if your shop is https://www.foxlabstudios.pl/, your configuration should look like this:
Domain: www.foxlabstudios.pl
SSL Domain: www.foxlabstudios.pl
Physical URI: /
Virtual URI: /Save any changes you make.

Step 2: Re-linking the ps_accounts Module
After correcting your shop URLs, you need to force ps_accounts to regenerate its OAuth client information:
- Switch your multistore context in the Back Office to the problematic shop.
- Go to Modules > Module Manager.
- Find the PrestaShop Account (
ps_accounts) module. - Click on the dropdown arrow next to the module and select Unlink.
- Clear your PrestaShop cache (Advanced Parameters > Performance > Clear Cache).
- Now, click on Link for the
ps_accountsmodule and attempt to log in again.
Step 3: Advanced Database Intervention (Use with Extreme Caution)
In some persistent cases, like dato_1234's eventual resolution via an "SQL query," stale or corrupted data in the database might prevent the fix. While the exact query wasn't shared, common areas to investigate (after a full database backup!) include:
ps_shop_urltable: Directly inspect and correct thedomainanddomain_sslcolumns for the affected shop ID.ps_configurationtable: Check for entries likePS_SHOP_DOMAINandPS_SHOP_DOMAIN_SSL, though these are typically overridden byps_shop_urlin multistore.- Module-specific configuration: Some modules might store domain-related settings in their own tables (e.g.,
ps_module_shopor custom tables).
Warning: Modifying the database directly without expert knowledge can lead to irreversible damage. If you suspect a database issue, it's highly recommended to consult a PrestaShop developer or a migration expert.
General Troubleshooting & Best Practices
- Clear Cache Religiously: Always clear PrestaShop's cache after making configuration changes.
- Verify SSL Certificate: Ensure your SSL certificate is valid and correctly installed for all domains.
- Check Server Configuration: Confirm that your server's
mod_rewriterules are correctly configured and that there are no conflicting redirects at the server level. - Module Updates: Keep all your PrestaShop modules, especially core ones like
ps_accounts, updated to their latest versions. - Staging Environment: Always test significant configuration changes or module updates in a staging environment before deploying to production.
Preventing Future Multistore OAuth Headaches
The best defense against these types of errors is a proactive approach to your PrestaShop multistore management:
- Consistent Domain Management: Maintain strict consistency in how you define and use your shop domains across all configurations (PrestaShop Back Office, DNS, server, SSL certificates).
- Regular Audits: Periodically review your shop URLs and module configurations, especially after migrations, server changes, or PrestaShop upgrades.
- Professional Setup: For complex multistore setups or migrations, consider engaging PrestaShop experts. Services like Migrate My Shop specialize in ensuring seamless transitions and optimal configurations, preventing such integration pitfalls.
The 'invalid_request' OAuth error in PrestaShop's ps_accounts module, particularly in a multistore context, is a testament to the precision required in e-commerce platform configuration. By understanding the dynamic nature of the redirect_uri and meticulously verifying your shop's domain settings, you can overcome this challenge and ensure your PrestaShop stores remain seamlessly connected. If you find yourself struggling with persistent integration issues or planning a complex migration, remember that expert assistance is just a click away at migratemyshop.com.