When attempting to access your website hosted on a DataPacket Linux plan, you might encounter a 503 Service Unavailable error on the frontend. On checking Plesk and your server logs, you may see one or both of the following error messages:
1. In the Plesk PHP Settings, the following error might be displayed:
Error: phpinimng failed: configuration test '['/opt/plesk/php/8.2/sbin/php-fpm', '--test']' failed with code 78, and message:[31-Oct-2023 06:09:37] ERROR: [pool yourdomain.com] cannot get uid for user 'username'[31-Oct-2023 06:09:37] ERROR: FPM initialization failed
2. In your site's log file, you might notice the following entry:
AH01079: failed to make connection to backend: httpd-UDS
Cause:
These errors are usually tied to corrupted PHP settings. The first message indicates that the PHP FastCGI Process Manager (FPM) can't initialize due to a misconfiguration or a missing user definition. The second log entry, "AH01079," suggests a failure in the communication between Apache's mod_proxy and the backend service, which could be related to the aforementioned FPM issue.
Resolution:
To address these errors and restore your website's functionality, follow the steps below. These actions will reset and rebuild your PHP configuration in Plesk:
1. Access Plesk Control Panel: Log into your Plesk control panel using your credentials.
2. Navigate to Hosting Settings: Within the panel, find "hosting settings".
3. Modify FastCGI Settings:
a. Locate the "fastcgi" option.
b. Uncheck the "fastcgi" box and click "save" or "apply."
c. After saving, recheck the "fastcgi" box and save or apply again.
4. Change PHP Version:
a. Head to the specific website or domain’s PHP settings within Plesk.
b. Temporarily switch the PHP version to another version and confirm the change.
c. After saving, revert the PHP version back to your original choice and save.
Carrying out these steps effectively instructs Plesk to reconstruct the PHP configuration for the specified domain or website. Upon completion, the 503 error on your site, as well as the backend PHP and AH01079 errors in your logs, should be resolved.
If these issues continue or if you experience other complications, don't hesitate to reach out to our support team for further help.
