Solved EzJail - apache24 + php56 E.O.L. phpinfo loads ... just not CMS Installer (Joomla or phpBB)

StreetDancer

StreetDancer

EzJail - apache24 + php56 E.O.L. phpinfo loads ... just not CMS Installer (Joomla or phpBB)

Does anybody know why? Is this an ezjail export setting that needs to be tweaked?

Example:

[Mod: URL removed] works just fine... However when I go to [Mod: URL removed] or [Mod: URL removed] both white screens regardless of the php-fpm pool working properly.

Thanks in advance!
 
Last edited by a moderator:
Lamia,

I am using phpbb3.1.x on alabama.wethepeopleonline.com/forum/ (only works on php5.6.x) which is why I am running php5.6 jailed. And the Joomla CMS rocketlauncher by RocketTheme; also told me it's php 5.6.x ready. I will turn on php.ini errors and see if it produces!
 
I just turned error reporting on; restarted and absolutely no errors. Just the white screen of death with a code 500 using inspect tools / network w/ firefox.
 
joneum,

I know this; that doesn't mean it just stops working! I have it in a jail because of lack of security updates. It clearly works phpinfo wouldn't load otherwise. There must be a solution.
 
We do not support software that is EOL.

The solution: Update php to a version of the 7.x branch and phpbb to the latest version. You can find everything in the ports.
 
StreetDancer said:
I just turned error reporting on; restarted and absolutely no errors. Just the white screen of death with a code 500 using inspect tools / network w/ firefox.
Click to expand...
500 is always fishing in muddy waters… And it's primary a *server* error, not a PHP error (but PHP-500 also exist…). Debugging this isn't fun, and maybe no one can solve this by giving you advice without sitting in front of it.

As a first step take a look at the requirements of your software - which Apache modules are required? I assume f.e. mod_rewrite. Also check the Apache settings belonging to "AllowOverride" (set it to "All" instead of the default "None") and the content of maybe existing htaccess files in the webspace.

Also take a look into your Apache logfiles. In such cases I'm tracing them in a separate terminal with "tail -f logfile" to see a little bit more of what's going on.

Backup your index.php file, and prepare it with echos and following exit - so you can see how far it is executed. Good luck…
 
StreetDancer said:
Lamia,

I am using phpbb3.1.x on alabama.wethepeopleonline.com/forum/ (only works on php5.6.x) which is why I am running php5.6 jailed. And the Joomla CMS rocketlauncher by RocketTheme; also told me it's php 5.6.x ready. I will turn on php.ini errors and see if it produces!
Click to expand...
Mind you given that php56 is EOL, you cannot just install it on a recent server. The 500 server is likely as a result of shared lib. error. You need to make sure the OS is at the version that Php56 was discontinued. That is just one of the several things to take note of.
 
Lamia said:
Mind you given that php56 is EOL, you cannot just install it on a recent server. The 500 server is likely as a result of shared lib. error. You need to make sure the OS is at the version that Php56 was discontinued. That is just one of the several things to take note of.
Click to expand...
Lamia,

I understand this! I used this special project on GitHub for FreeBSD and PHP 5.6.40

[Mod: URL removed, we don't support running EoL software]

The patch worked nicely and that's how I knew it worked when I can use console php:

php -v:

Code: 
root@php2:/usr/local/etc/apache24/Vhosts-Enabled # php -v
PHP 5.6.40 (cli) (built: Jul  5 2020 23:57:19) 
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

& the phpinfo page.

The modules compiled and everything! I enabled everything I normally do for my requirements of all my combination's of Joomla, 3rd Party Extensions. Just my premium themes for phpbb only work on 3.1 and 3.1 only works on php 5.6.

So... jails was the solution with that project for people like us I guess!

:)
 
Last edited by a moderator:
jmos said:
500 is always fishing in muddy waters… And it's primary a *server* error, not a PHP error (but PHP-500 also exist…). Debugging this isn't fun, and maybe no one can solve this by giving you advice without sitting in front of it.

As a first step take a look at the requirements of your software - which Apache modules are required? I assume f.e. mod_rewrite. Also check the Apache settings belonging to "AllowOverride" (set it to "All" instead of the default "None") and the content of maybe existing htaccess files in the webspace.

Also take a look into your Apache logfiles. In such cases I'm tracing them in a separate terminal with "tail -f logfile" to see a little bit more of what's going on.

Backup your index.php file, and prepare it with echos and following exit - so you can see how far it is executed. Good luck…
Click to expand...
jmos,

Indeed, very complex to diagnose. Thank you for chiming in regardless of my riskay E.O.L. php56 project.

Good suggestions. My apache 2.4.x configuration loads the following modules on start-up: (If you see anything out of place; please let me know, thanks!)

Code: 
LoadModule authn_core_module libexec/apache24/mod_authn_core.so
LoadModule authz_core_module libexec/apache24/mod_authz_core.so
LoadModule log_config_module libexec/apache24/mod_log_config.so
LoadModule expires_module libexec/apache24/mod_expires.so
LoadModule headers_module libexec/apache24/mod_headers.so
LoadModule version_module libexec/apache24/mod_version.so
LoadModule unixd_module libexec/apache24/mod_unixd.so
LoadModule vhost_alias_module libexec/apache24/mod_vhost_alias.so
LoadModule dir_module libexec/apache24/mod_dir.so
LoadModule rewrite_module libexec/apache24/mod_rewrite.so
LoadModule mime_module  libexec/apache24/mod_mime.so
LoadModule actions_module libexec/apache24/mod_actions.so
LoadModule alias_module libexec/apache24/mod_alias.so
LoadModule authz_host_module libexec/apache24/mod_authz_host.so
LoadModule access_compat_module libexec/apache24/mod_access_compat.so
LoadModule proxy_module libexec/apache24/mod_proxy.so
LoadModule proxy_fcgi_module libexec/apache24/mod_proxy_fcgi.so

I will take a look at the .htaccess also.
 
vigole said:
I'm not familiar with Joomla, but 500: Internal Server Error can be sign of permission error on php files. Try different chmod : 666 or 644.
Click to expand...
vigole,

I've done

Code: 
# chown -R www:www WTPO_alabama (apache's data folder) 
// doesn't resolve it.
also tried
Code: 
# chown -R root:wheel WTPO_alabama (apache's data folder)
// doesn't resolve it.
I set it back to www:www

I will try chmod permissions. I too have had experience with 500 producing based off chmod. Thank you for this!
 
Just be aware that it might be nothing to do with file permissions.

I think you need to do more digging to find out where the logs are going.

If you make your own page test_it.php with error_log("XXX TEST XXX") and visit it from a web browser - can you find that error log anywhere?
 
PhpBB 3.1 is EoL, PHP 5.6 is EoL. This is just an accident waiting to happen.
 
Okay; so in order to not waste anybodies time and for efficiency with a proper rule out. I went ahead and turned my jail #3 (all were clones) ; into a php 7.4.7 server. I then copied over the exact files in the exact folder structure and sure enough it processed. SirDice seems to be accurate on the E.O.L. disaster. I am troubled by these results as I do not understand why I can't run PHP 5.6.x isolated in a jail; it just seems to me there has to be a way to hack it up.

If anyone wants to continue to help and (richardtoohey) I will be doing the custom error logging attempt you suggested as it seems like the way to pin point hopefully a debug starting point.

Both servers remain online:

[Mod: Removed links]

Best Regards,

~ Brandon
 
richardtoohey2 said:
Just be aware that it might be nothing to do with file permissions.

I think you need to do more digging to find out where the logs are going.

If you make your own page test_it.php with error_log("XXX TEST XXX") and visit it from a web browser - can you find that error log anywhere?
Click to expand...
richardtoohey2,

I will find this out.
 
That's really smart. Posting the full URLs to websites that are running EoL software with known security issues on a public forum. Seriously, are you begging to get owned?
 
richardtoohey2,

test_it.php (I may have done this file incorrectly):

Code: 
<?php

error_log("TEST");
?>

Live link:
[Mod: URL removed]


Results: white screen & no log created called "TEST"
 
You have to investigate and find where PHP save error logs. If you are on a shared server, it can be in anywhere, /var/log/apache2 , ---, /usr/local/apache/logs/error_log, ....
If you don't have access to default location, try to save it another place, which you have access.
error_log("ERR\n", 3, "/somewhere/php.log");
The 2nd parameter (3): message is appended to the file.
You can use phpinfo() to find the path to php error message. But please don't do that, you've already shared too much info about your site in this public forum. I'm worried that you leave it untouched over there, ... and you can also, send it to an email address. But I don't suggest that either: It's probably unencrypted. Beside that, you have to set the right header in the message. Do yourself a favour, migrate to something else.

[EDIT]: If you have access to php.ini
Code: 
log_errors = On
display_errors = Off
display_startup_errors = Off
error_reporting = E_ALL
error_log = /pathToLog
string display_errors : whether errors should be printed to the screen.
boolean display_startup_errors : errors that occur during PHP's startup (whether errors should be printed to the screen.)
If error_log is commented out: errors will sent to the server log.
After changing php.ini you have to restart the web server
 
Lamia said:
And make sure all files & folders are owned by www.
Click to expand...
By now, this server is prolly owned by who-knows...

Really, update this box and disconnect while not done. EOL software like this is just plain dumb to be facing the 'net.
 
Thank you everyone! I will consider this solved and PHP 7.4.7 solved the issues. I will just scrap my 5.6 custom software.
 
You must log in or register to reply here.
Back
Top