After upgrading to 12.5 (wish we'd known it was in RTM status and not stable... the installer should provide a warning for this), and now none of our websites work (they're all 404)
Initially, I ran into this error:
In which I had to manually enable the alias module
Then, apache couldn't bind to port 80, so I had to manually disable the nginx reverse proxy in order to get apache to start/restart.
From there, all of our sites are returning 404 errors, even after having successfully regenerated our apache configs.
Did a little searching and ran the following as well (both successfully) to no avail:
/usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair
/usr/local/psa/admin/bin/httpdmng --reconfigure-all
No errors for either, but again after restarting apache2, all of my sites return 404.
So at this point, our entire server is essentially down since none of our websites can be accessed. So what do we do now?
Initially, I ran into this error:
Code:
AH00526: Syntax error on line 1 of /etc/apache2/conf-enabled/php_cgi_wrapper.conf:
Invalid command 'scriptAlias', perhaps misspelled or defined by a module not included in the server configuration
Warning : failed to perform deferred action : httpd_reconfigure
Trying to restart service apache2... Restarting web server: apache2 failed!
There are processes named 'apache2' running which do not match your pid file which are left untouched in the name of safety, Please review the situation by hand. ... (warning).
Then, apache couldn't bind to port 80, so I had to manually disable the nginx reverse proxy in order to get apache to start/restart.
From there, all of our sites are returning 404 errors, even after having successfully regenerated our apache configs.
Did a little searching and ran the following as well (both successfully) to no avail:
/usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair
/usr/local/psa/admin/bin/httpdmng --reconfigure-all
No errors for either, but again after restarting apache2, all of my sites return 404.
So at this point, our entire server is essentially down since none of our websites can be accessed. So what do we do now?
Last edited: