FastCGI troubleshooting Troubleshooting tips addressing common issues with FastCGI. Why does my application timeout on Apache?There are several reasons why a timeout occurs and both GAS and web server logs might need to be investigated.Why does my application not work with FastCGI?Incorrect FastCGI configurations and/or user permissions on directories and files are some of the most common reasons your application fails with FastCGI. Invalid installation directoryIf the FastCGI does not start and the Genero Application Server displays "Invalid installation directory", examine the environment and the GAS log directory permissions. Application URL not decodingIf the application URL does not decode correctly, examine the Apache configuration for mod_proxy_fcgi. File download fails due to spaces in filenameIf a file with a filename containing spaces is downloaded from an Apache 2.4 web server, the download may fail with a zero file size.Applications all down at the same time The most common application issues and how to resolve them are described.Why do my applications fail using multiple dispatchers?Make sure that each dispatcher has its own configuration file and its own session directory. Related conceptsUsing the FastCGI dispatcherRelated tasksRestarting fastcgidispatch without losing current sessionsConfigure FastCGI for Apache prior to 2.4Configure FastCGI for Apache 2.4