NGINX connection refused

All you need to configure a website for Laravel app can de done easily right from within ISPConfig. No need to edit any config files manually or change permissions of folders. You did a lot of things to forcefully destroy your server, starting with changing permissions of a website to editing vhost files and then removing vhosts incl. all config that ISPConfig needs and which can not be restored automatically doing an ISPConfig update. Also you should not have created a database manually. You have to undo all these steps now to fix it, especially deleting this messed up website from within ISPConfig to be able to create a new working one. Do you have a backup of your server that you can restore?

If you do not have a backup of the system, check folder /var/backup, it might contain a folder named ispconfig which then contains at least a backup of the /etc from where you can restore the nginx config files you deleted. After restoring the Nginx config files, you should be able to log into ISPConfig where you can delete that website and create it again. Then manually delete that mysql database you created for the site and create one in ISPConfig instead. When you fixed the system until that stage, then we can help you with the steps for the final preparation of that site for Laravel.

 

The server is not fully destroyed. But we have to try to recreate the ispconfig vhost manually now to get the interface up again. Whats in /etc/nginx/sites-available/ now and whats in /etc/nginx/sites-enabled/ ?

 

Create a new file:

/etc/nginx/sites-available/ispconfig.vhost

with this content:

Code:

server {
        listen 8080 ssl;
        listen [::]:8080 ssl ipv6only=on;

                ssl_protocols TLSv1.2;
        ssl_certificate /usr/local/ispconfig/interface/ssl/ispserver.crt;
        ssl_certificate_key /usr/local/ispconfig/interface/ssl/ispserver.key;
        ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';
        ssl_prefer_server_ciphers on;

                # redirect to https if accessed with http
                error_page 497 https://$host:8080$request_uri;

        server_name _;

        root   /usr/local/ispconfig/interface/web/;

        client_max_body_size 20M;

        location / {
               index index.php index.html;
        }

        # serve static files directly
        location ~* ^.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt)$ {
               access_log        off;
        }

        location ~ \.php$ {
               try_files $uri =404;
               include /etc/nginx/fastcgi_params;
               fastcgi_pass unix:/var/lib/php7.3-fpm/ispconfig.sock;
               fastcgi_index index.php;
               fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
               #fastcgi_param PATH_INFO $fastcgi_script_name;
               fastcgi_buffer_size 128k;
               fastcgi_buffers 256 4k;
               fastcgi_busy_buffers_size 256k;
               fastcgi_temp_file_write_size 256k;
               fastcgi_read_timeout 1200;
                           fastcgi_param HTTP_PROXY "";
        }

        location ~ /\. {
               deny  all;
        }

#        location /phpmyadmin {
#               root /usr/share/;
#               index index.php index.html index.htm;
#               location ~ ^/phpmyadmin/(.+\.php)$ {
#                       try_files $uri =404;
#                       root /usr/share/;
#                       include /etc/nginx/fastcgi_params;
#                       fastcgi_pass unix:/var/lib/php7.3-fpm/ispconfig.sock;
#                       fastcgi_param  HTTPS on;
#                       fastcgi_index index.php;
#                       fastcgi_param SCRIPT_FILENAME $request_filename;
#               }
#               location ~* ^/phpmyadmin/(.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt))$ {
#                       root /usr/share/;
#               }
#        }
#        location /phpMyAdmin {
#               rewrite ^/* /phpmyadmin last;
#        }
#
#        location /squirrelmail {
#               root /usr/share/;
#               index index.php index.html index.htm;
#               location ~ ^/squirrelmail/(.+\.php)$ {
#                       try_files $uri =404;
#                       root /usr/share/;
#                       include /etc/nginx/fastcgi_params;
#                       fastcgi_pass unix:/var/lib/php7.3-fpm/ispconfig.sock;
#                       fastcgi_param  HTTPS on;
#                       fastcgi_index index.php;
#                       fastcgi_param SCRIPT_FILENAME $request_filename;
#               }
#               location ~* ^/squirrelmail/(.+\.(jpg|jpeg|gif|css|png|js|ico|html|xml|txt))$ {
#                       root /usr/share/;
#               }
#        }
#        location /webmail {
#               rewrite ^/* /squirrelmail last;
#        }
}

Then run:

Code:

cd /etc/nginx/sites-enabled/
ln -s /etc/nginx/sites-available/ispconfig.vhost 000-ispconfig.vhost
service nginx restart

then you can try to login to ISPConfig. If this works, delete that site in ISPconfig. Afterwards choose Tools > resync in ISPConfig and let it resync the websites.

 

1) Create a database and database user in ISPConfig.
2) Create a website in ISPConfig, enable PHP for that website. Then go to the options tab and change the document root of the site. E.g. if your laravel app wants to use public/html, then you enter this in the Nginx directives field on the options tab of the website:

Code:

##subroot public/html ##

3) Now create an SSH user for the site, log in with that SSH user, and start installing your Laravel app inside the site's web folder. You likely want to choose an SSH user without chroot, as this will make things easier and allow that user to use the globally installed composer.

There is no need to alter any folder owners etc. as the SSH user is already the same user that runs PHP in that site.

 

That's because the dev does not know that there are Hosting Control Panels like ISPConfig which set correct permissions on their own. The PHP process runs under the same user that you use to upload, so there are no permissions that need to be changed, especially not to ww-data as websites do not run as www-data.

That's not related to ISPConfig and only the person who developed that application can help you there and tell you what "sss" means in his app. If its a Laravel app, you need the subroot, otherwise the web server will load content from web folder and not web/public/ folder.