• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Inconsistent PHP file updates across domains using same vhost

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.73 Update #3
I recently ran into a strange issue and I’m not entirely sure what caused it, ...

Yesterday, I updated (uploaded) a PHP file on the server. I have multiple domains pointing to the same vhost (with identical content). However, one of the domains kept showing as output an outdated (previous) version of the file.

In my setup, two domains use “8.4.14 Dedicated FPM application” and four domains use “8.4.14 FPM application.”
The issue occurred on only one of the domains using the “Dedicated FPM application” mode. I was able to fix it by simply opening and re-saving the file via sFTP, after that, the correct version was immediately displayed.

... so I wanted to ask if anyone else has experienced something similar? Could this be a PHP issue, or is there possibly a misconfiguration in Plesk?
 
If I recall correctly, running a dedicated FPM application makes a pool which loads the file into memory and keeps it into memory. If you restart the dedicated FPM application after uploading the edit file chances are the new changes will reflect just fine.

What you'll want to do if you must use a dedicated FPM application and you're using opcache is to add opcache.revalidate_freq=5 (opcache is usually on by default and you can add that line in domains > domain in question > php settings in the additional directive section)
 
Back
Top