I just did a fresh install of WordOps, it appeared to only come with PHP 8 so afterwards I manually installed php7.4 with all the extensions I will be needing from apt. Before I created any site, the domains pointing the server did display the nginx welcome page.
Then I created two sites, one will not be a WordPress site so I used the command "wo site create site1.tld --php74 --mysql -hsts". Then I created a new WordPress site using "wo site create site2.tld --php74 --wpredis --hsts" and if I try to access it I simply get a 503 error. If I throw a test index.html in the first site I do get the file served, but if I put a test php file I have the same issue as the WordPress site.
I've restarted nginx, php7.4-fpm and mysql/mariadb many times through out debugging.
I checked the nginx logs and it shows that it cannot access the php7.4-two-fpm.sock so I checked out the /var/run/php location and there is a php7.4-fpm.sock but there is not a php7.4-two-fpm.sock in there... I tried to find in the nginx config files where the fastcgi_pass unix would be to simply try and change this to the sock that actually exists, but I cannot find a reference at all. I used grep to search the nginx directory for 'fastcgi_pass unix' and only found the line in the default nginx site file that is commented out anyway and searching for 'php7.4-two-fpm' found nothing.
Also the in /etc/php/7.4/fpm/pool.d/www.conf is configure for listen = /var/run/php/php7.4-fpm.sock no 'two' there, so I have no idea why the error logs say it's looking for php7.4-two-fpm.sock
The nginx error is:
[crit] 1369#1369: *105 connect() to unix:/var/run/php/php74-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: myserver.tld, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php74-fpm.sock:", host: "myserver"
[error] 1369#1369: *105 no live upstreams while connecting to upstream, client: 188.8.131.52, server: myserver.tld, request: "GET / HTTP/2.0", upstream: "fastcgi://php74", host: "myserver.tld"
So I need to either understand how WordOps has modified the nginx config so I can point it to the correct sock, or I need to figure out how to create the missing php7.4-two-fpm.sock, bonus points if someone can also help me understand why this even happened. I could just start over at this point, there isn't anything on this server, but it seems to be almost working and I'm more curious why it isn't and how to fix it as this is not the first time I used WordOps and it worked great for me before.