- Plesk 12.5 for Linux
- Plesk Onyx for Linux
Website inaccessible with the following error:
CONFIG_TEXT: Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
- A website on Magento is inaccessible with the error:
Website name contains upper-case letters and it is using Apache + PHP-FPM.
The following error can be found in
CONFIG_TEXT: [proxy:error] [pid 11255] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /home/httpd/vhosts/system/example.com/php-fpm.sock (*) failed
[proxy_fcgi:error] AH01079: failed to make connection to backend: httpd-UDS, referer: https://example2.com/profiles/ticket/XJ-447-329/conversation
- Domain reconfiguration fails:
CONFIG_TEXT: ERR [panel] Apache config generation failed: Template_Exception: mkdir: cannot create directory `/var/www/vhosts/system/Example.com/conf': No such file or directory mktemp: failed to create file via template `/var/www/vhosts/system/Example.com/conf/httpd.conf.XXXXXX': No such file or directory Can not create temporary file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php line: 75 code: 0 mkdir: cannot create directory `/var/www/vhosts/system/Example.com/conf': No such file or directory mktemp: failed to create file via template
- #PPPM-4284 "[ FireStorm GmbH ] Websites with uppercase letters are not working if they are configured with handler Apache+PHP-FPM"
- Plesk Obsidian 02 July 2018 (fixed as PPP-25110)
If update is not possible for some reason you may try the following
Upgrade to Plesk Obsidian Release Candidate 1.0 which is currently available for early adopters.
If upgrade is not possible, as a workaround do the following:
- Log into Plesk UI.
- Go to Plesk > Domains > example.com > PHP Settings and change PHP handler to PHP FastCGI or PHP FPM served by nginx.
Recreate or rename the subscription using lowercase letters only. The renaming can be done at Subscriptions > example.com > Domains > Hosting Settings. Since direct renaming will throw the "domain name already exists" error, use the following scheme: example.com - example2.com - example.com.