PHP still runs old code after deploy (OPcache not reset)
OPcache keeps serving cached bytecode, so changes uploaded to the server don’t take effect.
Exact message you may see
OPcache stale codechanges not showing PHP
Seen on:
PHP
Meaning
With opcache.validate_timestamps=0 (common in production) PHP never checks files again until FPM restarts or the cache is reset. Symlink-swap deployments also confuse realpath caches.
Common causes
- validate_timestamps disabled
- Deploy without reloading PHP-FPM
- Symlink-based deploys with realpath cache
⚡ Quick fix
- Reload PHP-FPM after each deploy (
systemctl reload php8.2-fpm) - Call
opcache_reset()via a protected endpoint - Use
$realpath_rootin Nginx for symlink deploys
Detailed fix by platform
Nginx
fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
How to diagnose
- Setting — opcache.validate_timestamps value
- Deploy — Is FPM reloaded?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PHP
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026