Hello... in the last years I setup my servers always with the The Perfect Server - Ubuntu 18.04 (Bionic Beaver) setup... Always it's working... But on my new server I can't install a Wordpress with the APP installer... I solved this tutorial now 5 times and this server want work... I setup only one client and one page... with php-fpm... welcome to your site... than i want to installing Wordpress with the APP installer.. I become: ERROR 503 - Service Unavailable! The following error occurred: The Service is not available at the moment due to a temporary overloading or maintenance of the server. Please try again later. Please contact the webmaster with any queries. and a installation error... the c1aps1 dbuser is created but not the DB... and if I want to install manually a Wordpress with a duplicator file from my Wordpress: I don't have rights in /client1..../web i do exactly the same like the last years but this server want work... for any help im happy...
APS are not provided by ISPConfig but by 3rd party apscatalog.com This project is discontinued (see: https://www.cloudblue.com/aps-standard) I have read somewhere, that the support will be removed from future ISPC versions. So probably the Wordpress installation via APP install is outdated. Just install it the manual way: https://wordpress.org/support/article/how-to-install-wordpress/
The website settings must be like this: Suexec checkbox must be enabled. PHP mode must be php-fpm or php-fcgi if these requirements are met, then PHP can write into the web folder. For uploading Wordpress to the web folder, create a FTP user for this website in ISPConfig.
Thanks for all answers... the pages are running again... but only with mod-php or fast-cgi... if I choose php-fpm I become always: ERROR 503 - Service Unavailable! The following error occurred: The Service is not available at the moment due to a temporary overloading or maintenance of the server. Please try again later. Please contact the webmaster with any queries.
I am having the EXACT SAME problem. php-fpm keeps coming up with the 503 Error. Did you find a solution for fixing this problem with PHP-FPM?
I figured it out. It was a problem with the CMS and the way I imported the database. The ISPConfig 503 Error seems very broad (covers a lot of things). I wish it could be more detailed.