When attempting to run my script, which worked flawlessly on fcgi i’m encountering 500 followed by:
[Sun May 03 13:11:38.376439 2020] [proxy:warn] [pid 4733] [client 195.112.122.110:60430] AH01144: No protocol handler was valid for the URL /index.php (scheme '|fcgi'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Sun May 03 13:11:38.750641 2020] [proxy:warn] [pid 4732] [client 195.112.122.110:60432] AH01144: No protocol handler was valid for the URL /index.php (scheme '|fcgi'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule., referer: http://<domain>
when trying to actually get the list of apache modules installed via apache2 -M i get the following:
[Sun May 03 13:18:29.139135 2020] [core:warn] [pid 8538] AH00111: Config variable ${APACHE_PID_FILE} is not defined
[Sun May 03 13:18:29.139535 2020] [core:warn] [pid 8538] AH00111: Config variable ${APACHE_RUN_USER} is not defined
[Sun May 03 13:18:29.139663 2020] [core:warn] [pid 8538] AH00111: Config variable ${APACHE_RUN_GROUP} is not defined
[Sun May 03 13:18:29.139784 2020] [core:warn] [pid 8538] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
[Sun May 03 13:18:29.161383 2020] [core:warn] [pid 8538] AH00111: Config variable ${APACHE_RUN_DIR} is not defined
AH00543: apache2: bad user name ${APACHE_RUN_USER}
Without serverside debuging, I don’t think we can help you out with your script. Infact this isnt a hestia sided issue, you’ll need to find a sysadmin to help you out here.
Or maybe another user of the community can help you out?
That we can’t help out without additional informations or a server sided debugging? yes
This is both possible, the services are running in default stack and can be adjusted like you want. But we can’t do that adjustment for you, this is a part on your side as admin .
So you are saying that bundling hestiacp with php-fpm was an outstanding move? How preposterous. At least you could bundle it with both php-frm and fcgi. Given that there’s multiphp there should be a way to switch between versions anyway.
Of course, that’s why we got now a fast and reliable multiphp stack.
You’re free to help us out developing also multiphp using fcgi, just checkout the code and send us a pull request. That it isnt there doesnt mean that we do not want to have it, mostly it is just a time based issues - all members that are working on this project, do this for free - beside their 100% job.
Also fcgi wasnt disabled at all, probaly you just need to create a custom template to get it working - but I can’t guide you how to do it, because I do not know your system and requirements from your script. It completly depends on what you want to do.
my requirements == same as vestacp defaults (since it was installed beforehand until exim4 broke) + fresh 7.3 install with most of the php modules, as for system - same specs as the other box, same ubuntu 18.04.4LTS, same 2gb ram, different boxes tho
and no, i’m afraid i can’t push changes in bash scripts/complex configs/templates since i’m a strictly a php/mysql dev
-Can you share the composer file for that script so I can check on a test install?
-Do you have the same problem with a minimal php script (like a hello-world) ?
-Is there a .htacces file in public_html folder?
-Are you using a default apache template or a custom one?