Feeling Lucky
?
[#24125] - Internal Server Error instead of Joomla error page on PHP-FPM
- Closed
- 25 Mar 2019
- Medium
- Build: staging
- # 24125
Steps to reproduce the issue
Run Joomla on PHP-FPM setup.
Cause an error, e.g. put a call to non-existing function in templates/protostar/index.php.
Expected result
Joomla error page. With stack trace if debug is enabled.
Actual result
Internal Server Error.
System information (as much as possible)
| Setting | Value |
|---|---|
| PHP Built On | Linux 2.6.32-042stab134.8 #1 SMP Fri Dec 7 17:16:09 MSK 2018 x86_64 |
| Database Type | mysql |
| Database Version | 5.5.5-10.3.12-MariaDB |
| Database Collation | latin1_swedish_ci |
| Database Connection Collation | utf8mb4_general_ci |
| PHP Version | 7.3.2 |
| Web Server | Apache/2 |
| WebServer to PHP Interface | fpm-fcgi |
| Joomla! Version | Joomla! 3.9.3 Stable [ Amani ] 12-February-2019 15:00 GMT |
| Joomla! Platform Version | Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT |
Additional comments
Not a solution, but replacing $app->toString() with $app->getBody() here displays the error page normally. So maybe this is something to do with sending headers:
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Title |
|
||||||
| Status | New | ⇒ | Discussion |
SharkyKZ
- comment
- 25 Mar 2019
Closing this as per #24183 (comment) it's a server configuration issue.
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-03-25 17:49:38 |
| Closed_By | ⇒ | SharkyKZ |
@SharkyKZ can you please give the Issue a Categorie on Issue Tracker? I have no clue where to assign.