• 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.

PHP Not Functioning for Virt. Hosts

C

curtis

Guest
Our Windows Plesk box does not process PHP scripts for client domains. The administrative interface works fine, and so does webmail, but client domains time out with a 'Bad Gateway' error on the simplest of PHP scripts.

The Plesk box reports its version as 'psa v7.5.6 build20051107.20 on Windows5.2.3790.0', and we have not upgraded PHP. Reconfigurator doesn't seem to help the problem.

Thanks,
Curtis
 
Solved. php_curl.dll wasn't loading, and commenting it out of c:\windows\php.ini fixes it. I'll probably grab a fresh copy when I get a chance.

- Curtis
 
I am also running: psa v7.5.6_build20051107.20 os_Windows 5.2.3790.0

I too get the bad gateway error. But when I commented the dll out of php.ini, I still get the error. Has it ever come up for you again? How did you find out that the dll wasn't loading?
 
This hasn't happened again since. I'm pretty sure that the error was either displayed in 'Event Viewer', or I found it by trying to run a php script from the command line (http://us3.php.net/features.commandline).

You probably have a different DLL corrupted, or a configuration error preventing php from running I would guess.

Thanks,
Curtis
 
Back
Top