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

FastCGI timeout

G

GermainS

Guest
Hello, im trying to edit FastCGI timout becouse my PHP script tells my PHP-CGI.exe timout has exceeded

I've Searched everywhere for the awnser to this question and im getting only Linux info or links to tutorials wich have different paths to different files and none work.

I hope you guys can help me out.

*need to increase the the fastCGU timeout

System: Windows 2008 R2
Plesk : 10
 
Last edited by a moderator:
The problem is i cant find this file
Windows\System32\inetsrv\fcgiext.ini
 
Last edited by a moderator:
Looks like (x86) should be backslashed. Read about regular expressions syntax.
 
Ah i found it, instead of using qoute i needed doubleqoute's

Inserted this line

C:\Windows\system32>%windir%\system32\inetsrv\appcmd set config -section:system.webServer/fastCgi -[fullPath="C:\Program Files \(x86\)\Parallels\Plesk\Additional\PleskPHP5\php-cgi.exe"].activityTimeout:600


now im getting this error

ERROR ( message:Malformed collection indexer; format is [@position,name='value',
name2='value2',...]. The @position specifier is optional, and be '@start', '@en
d', or '@N' where N is a numeric index into the collection. )
 
Last edited by a moderator:
I had this time out issue and it was after an upgrade.
It seems one of my sites had some old IP associated with it in IIS.
Once I changed IP's everything worked fine.
 
Back
Top