Starting with FreePBX Framework 13.0.182 and Core 13.0.112 FreePBX added ModRewrite-Statements to Admin htaccess
Problem:
Updating FreePBX will result in an "Internal Server Error" caused by unknown command "RewriteEngine"
Reason:
Apache in RasPBX distro is missing mod_rewrite
Solution:
SSH to your RasPBX
Type
a2enmod rewrite
and restart Apache
service apache2 restart
FreePBX Admin will open without any errors afterwards.
Prediction:
Every RasPBX Installation will fail within the next days after every system has been updated to the latest Core/Framework which is mandantory because of a code execution security breach.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the explanation why this is not activated by default is that they are trying to keep the base load of the system as low as possible. As long as there's no need for mod_rewrite there's no reason to activate it by default.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Patch is uploaded: Upgrade #24 enables the rewrite module. However, users will have to run raspbx-upgrade first, then the FreePBX upgrades, otherwise the gui still breaks. But a broken gui will be fixed by just enabling the rewrite module.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got hit by this. Thanks for the a2enmod work-around.
You say run raspbx-upgrade first then the updates. What if you've already installed the FreePBX updates? Will running raspbx-upgrade be enough to fix this problem for the future?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it will also fix the problem after you've installed the FreePBX upgrades, and thus will fix your broken gui. raspbx-upgrade just calls the a2enmod as stated above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Starting with FreePBX Framework 13.0.182 and Core 13.0.112 FreePBX added ModRewrite-Statements to Admin htaccess
Problem:
Updating FreePBX will result in an "Internal Server Error" caused by unknown command "RewriteEngine"
Reason:
Apache in RasPBX distro is missing mod_rewrite
Solution:
SSH to your RasPBX
Type
and restart Apache
FreePBX Admin will open without any errors afterwards.
Prediction:
Every RasPBX Installation will fail within the next days after every system has been updated to the latest Core/Framework which is mandantory because of a code execution security breach.
Same here, happens still after some more recent updates and breaks the PBX. Very confusing how this could have been missed.
I think the explanation why this is not activated by default is that they are trying to keep the base load of the system as low as possible. As long as there's no need for mod_rewrite there's no reason to activate it by default.
I will deliver a patch for this asap, so it will be fixed with the usual raspbx-upgrade. Will keep you posted.
Patch is uploaded: Upgrade #24 enables the rewrite module. However, users will have to run raspbx-upgrade first, then the FreePBX upgrades, otherwise the gui still breaks. But a broken gui will be fixed by just enabling the rewrite module.
I got hit by this. Thanks for the a2enmod work-around.
You say run raspbx-upgrade first then the updates. What if you've already installed the FreePBX updates? Will running raspbx-upgrade be enough to fix this problem for the future?
Yes, it will also fix the problem after you've installed the FreePBX upgrades, and thus will fix your broken gui. raspbx-upgrade just calls the a2enmod as stated above.