Client call
"Since last night, I reach the admin login, I enter my credentials, then blank page. Front OK, orders keep coming in."
🔒 No more admin access · Recovery < 1 h
Your PrestaShop admin
Your PrestaShop admin
has become unreachable?
we recover access today.
PrestaShop back-office access recovery when admin is locked
Forgotten /admin-xxx URL, lost password, blank screen after login, 403 on the dashboard, infinite redirect:
your front works, but you are locked out of the back-office.
We come in via SSH or phpMyAdmin, identify the lock, hand the key back to you.
✓ Free diagnostic
✓ Firm quote within 24 business hours
✓ From €60/h excl. VAT
✓ Your data intact
🩺 Quick diagnostic
What you see = the likely cause
Spot your symptom in the table. Diagnostic is narrowed down in under a minute.
🔎 The real causes
Why a BO becomes unreachable in 2026
Distribution observed across 22 BO access recoveries delivered in 2025-2026.
1. Lost password / URL (≈ 30%)
You haven't touched the BO in 6 months, the browser flushed its auto-fill, and the /admin-XXXX URL with its hash is long gone. The simplest case to solve — 15 min via SSH or phpMyAdmin to find the URL and reset the password in SQL.
2. Recently installed BO module (≈ 22%)
You installed a module the night before, and since then the admin has been blank from login on. The module hooks into actionAdminControllerInitBefore or a BO widget and crashes. Fix: identification via logs or bisection, SQL disable.
3. Broken admin override after update (≈ 18%)
A PrestaShop update (1.7 → 8, 8.x → 9) changes the signature of an admin controller method. Your override in /override/controllers/admin/ inherits from the parent class, no longer matches the signature, and crashes on load.
4. IP blocked by security (≈ 12%)
You tried to log in 5 times with the wrong password, a "Brute Force Protect" type module (or Cloudflare WAF) temporarily banned you. The BO returns 403 even if you reach the URL. Fix: temporary whitelist of your IP.
5. HTTPS / HTTP redirect loop (≈ 10%)
You enabled Let's Encrypt on the front but forgot to update PS_SHOP_DOMAIN_SSL in ps_configuration. The BO redirects HTTP to HTTPS then HTTPS to HTTP in an infinite loop. Browser gives up with ERR_TOO_MANY_REDIRECTS.
6. Invalid Symfony container (PS 8/9) (≈ 8%)
Specific to modern versions. A module declares a service with a phantom dependency in services.yml, or a typed argument that doesn't exist. Symfony refuses to boot the BO without breaking the front (which uses a different kernel).
⚡ Typical intervention
Admin recovered in 42 min
Real case · Home decor shop · PrestaShop 8.0 + 28 modules · December 2025.
SFTP access obtained · debug enabled
Editing
app/config/parameters.php: '_PS_MODE_DEV_' => true. Refresh login page + new sign-in.
Readable error
Fatal error: Uncaught Error: Call to undefined method ToolsCore::displayPriceSmarty() in /modules/dashboardproduct/dashboardproduct.php:117. Core method no longer exists in PS 8.
Hypothesis confirmed
Module
dashboardproduct last updated 2018, incompatible with PrestaShop 8.0. The method was renamed Tools::displayPrice().
SQL disable of the module
phpMyAdmin →
UPDATE ps_module SET active = 0 WHERE name = 'dashboardproduct';. Cache flushed. New admin sign-in: dashboard loaded.
Debug disabled + report
Debug set back to
false. Email sent: timeline + cause + recommendation (replace dashboardproduct with PS 8 native equivalent or patch the code).
42 min
Recovery time
~ €42
Billed on quote
(42 min × €60/h excl. VAT)
(42 min × €60/h excl. VAT)
0
Data lost
💰 Pricing
Pricing stated up-front
Free diagnostic. For the intervention, you know exactly what it costs before we touch the code.
🔍 Diagnostic
Diagnostic
find the lock
0€free
30 min · no commitment
- BO test on 3 browsers + 2 IPs
- Log reading and review of
ps_module - Firm quote sent immediately
- You decide if we continue
⚡ Most requested
🔧 Intervention
Targeted intervention
restore admin access
from 60€excl. VAT
per diagnostic · price stated up-front
- Backup files + DB before any intervention
- Reset password / URL / IP / module / override
- Tests login + full BO navigation
- Written report: root cause + fix applied
- 30-day warranty on the fix
🛡️ Maintenance
Monthly maintenance
BO monitoring + backup access
from 50€/ month
24/7 monitoring · no commitment
- KLN backup admin account on your store
- Daily backups automated, externalised
- Override audit before every PrestaShop update
- Priority intervention if BO unreachable
🧭 Don't confuse with
"BO unreachable" is not...
❌ Not an entirely down site
If both front and BO are unreachable, it's a server / host issue, not BO-specific. Dedicated page.
PrestaShop down page → ❌ Not a front white screenIf the front is also a white screen, it's a broader PrestaShop application bug, not a BO authentication issue. Dedicated page.
White screen page → ❌ Not a hackIf your admin login was changed without your consent (you see "invalid credentials" with your real ones), it's likely a hack. Different protocol.
Hacked site page →
❓ FAQ
PrestaShop BO unreachable — frequently asked questions
Six causes cover 95% of cases: (1) lost password or disabled account, (2) forgotten admin URL (PrestaShop adds a hash to
/admin-XXXX/), (3) corrupted session cookie after a move or domain change, (4) BO module crashing only on admin side, (5) broken admin controller override after update, (6) IP blocked by security after failed login attempts. Diagnostic via error_log + IP check from firewall.Three methods: (1) FTP: list the root, look for a folder starting with
admin followed by characters. (2) Database: phpMyAdmin → ps_configuration, some security modules store the admin URL there. (3) PrestaShop welcome email: on install, PS sends an email containing the full URL. If all three fail, we recover it in 5 min via SSH.(1) "Forgot password" link from the BO if email is valid and
sendmail works. (2) If email doesn't go out: direct SQL reset — phpMyAdmin → ps_employee → overwrite passwd with a generated bcrypt hash. (3) Temporary PHP script calling the PrestaShop API. Methods 2 or 3: 10 min.Login succeeds but the dashboard doesn't render. Five causes: (1) recently installed BO module crashing when loading admin — disable via SQL
UPDATE ps_module SET active=0. (2) override of AdminDashboardController broken after update — neutralise /override/controllers/admin/. (3) custom BO widget throwing a silent fatal. (4) On PS 8/9: invalid Symfony container. (5) corrupted admin cache — delete /var/cache/prod/. Universal: enable debug mode for 5 min to see the real error.Depending on cause: URL/password: 15-30 min. IP blocked: 15 min. BO module crashing: 30 min to 1 h. Broken override: 1 to 2 h. Symfony container (PS 8/9): 1 to 3 h. Overall, 80% of cases in under an hour once the diagnostic is done.
No, we need at minimum server access (FTP, SFTP, SSH or cPanel). If you've lost every credential, the first step is to recover them from your host (1 to 4 h with ID). We guide you on WhatsApp through the process. Once any access is recovered (even limited), we start the diagnostic.
🔗 Related topics
Other issues I handle
Locked out of your PrestaShop admin?
Free 30-min diagnostic. We identify the lock, quote it, you decide. Firm quote within 24 business hours.