Short answer: you'll need to manually make changes to your Apache config.
Long answer is that the Debian upgrade scripts won't touch your config by default. It should give you the option of accepting the new/updated config scripts of anything you've adjusted. But allowing it to do that, it will wipe out your customisations. Even if you allow it to update all the config, there may be new files that have been added that will still require adjustments (as they may clash with updated config). So either way, you will almost certainly need to manually update the Apache config so that it works for you and is compatible with the new Apache 2.4 format. I know it's a pain, but it's a necessary evil.
OTTOMH one major thing that has changed is that all Apache config files now need to have a .conf file extension. So if any of your custom/non-default config files don't yet have that, rename them so they do.
There are also a number of directives that have somewhat changed. When I upgraded the TurnKey library to v14.0, I found the Apache upgrade docs invaluable (and helped me resolve all the issues I hit). This Digital Ocean tutorial is also pretty good too IMO.
Checking the Apache logs (i.e. tail /var/log/apache2/error.log) and/or running a config test (i.e. apachectl configtest) should help you pinpoint exactly where the problems lay.
However, if you can post your problematic Apache config files, I'm more than happy to help you make the required modifications. Beyond the logs, one of the first things to check is the "virtual hosts" you have enabled. Have a look in /etc/apache2/sites-enabled. I.e.:
ls /etc/apache2/sites-enabled
Then cat each of those files and post back here. Feel free to also post the Apache log (or at least the last few lines) and/or the output of apachectl configtest.
Hi David
Short answer: you'll need to manually make changes to your Apache config.
Long answer is that the Debian upgrade scripts won't touch your config by default. It should give you the option of accepting the new/updated config scripts of anything you've adjusted. But allowing it to do that, it will wipe out your customisations. Even if you allow it to update all the config, there may be new files that have been added that will still require adjustments (as they may clash with updated config). So either way, you will almost certainly need to manually update the Apache config so that it works for you and is compatible with the new Apache 2.4 format. I know it's a pain, but it's a necessary evil.
OTTOMH one major thing that has changed is that all Apache config files now need to have a
.conffile extension. So if any of your custom/non-default config files don't yet have that, rename them so they do.There are also a number of directives that have somewhat changed. When I upgraded the TurnKey library to v14.0, I found the Apache upgrade docs invaluable (and helped me resolve all the issues I hit). This Digital Ocean tutorial is also pretty good too IMO.
Checking the Apache logs (i.e.
tail /var/log/apache2/error.log) and/or running a config test (i.e.apachectl configtest) should help you pinpoint exactly where the problems lay.However, if you can post your problematic Apache config files, I'm more than happy to help you make the required modifications. Beyond the logs, one of the first things to check is the "virtual hosts" you have enabled. Have a look in
/etc/apache2/sites-enabled. I.e.:Then
cateach of those files and post back here. Feel free to also post the Apache log (or at least the last few lines) and/or the output ofapachectl configtest.