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

Still having problems running scripts

C

colinjack

Guest
We are runniing 7.5.6 on Server 2003

As a rule we recommend that all scripts (php, pl, cgi etc) are run from clients' /cgi-bin. Unfortunately some clients report that when running PHP scripts they get a login dialog - not all clients have this problem, but most. Permissions all look fine etc. (read/execute)

We have posted this before but not had a resolution. Anybody any ideas?

:confused:
 
Even more bizarre is that if I set PHP to run as an ISAPI extension then it effectively 'kills' the site (browser returns blank pages for .html) ... but the .php script doesn't return a login dialog.

Weird - especially as not all sites are affected (although most)
 
No ... I am still trying to get around it. It has something to do with the way Plesk applies the permissions, but even setting them manually hasn't sorted it. Odd.
 
well i figured it out on my server so hopefully its the same for you. Go to your perl directory (mine is program files/plesk/additional/perl I think)... check the perms on that folder. Chances are if you have the same problem as me, you need to add the IUSR group to it, just needs read execute and you should be in business. Hopefully you have the same problem as I did.


Aaron
 
Aaron you bloomin' star :D

I have been looking in totally the wrong area - checking folder permissions etc. Didn't for a minute think Plesk would be dim enough to not allow the IUSR group execute permissions to the progs in the additionals. Doh!

Well done.

Colin
 
Plesk grants access permission on Additional folder be default and they can't be reset by Plesk. Only manually.

But you can restore default Plesk permission on all Plesk folders using Plesk reconfigurator.
 
I had already tried the reconfigurator and it hadn't fixed it. I have been battling with this problem for months and nobody from Plesk even suggested checking this.
 
Yeah Oleg, your reconfigurator didnt fix the problem for us either... perhaps something else to check for a future revision.

Glad to hear it worked for ya colin

Aaron
 
Back
Top