Support

Admin Tools

#16417 Blocked IP's / users get an internal server error message

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Monday, 17 June 2013 07:13 CDT

JosBlo
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes / WAF
Joomla! version: 2.5.11
PHP version: 5.3.16
MySQL version: 5.1.68 ??
Host: Siteground VPS
Admin Tools version: 2.5.5

Description of my issue:

When an IP / User is blocked because of a wrong login, he get an Internal Server 500 error instead of the message entered in the backend for blocked IP's.

What am i doing wrong?

Best regards,

Jos

nicholas
Akeeba Staff
Manager
A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):
ini_set( 'display_errors', true );
error_reporting( E_ALL ); 
Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:
php_flag display_errors On
php_value error_reporting 32767
and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

IMPORTANT: Sometimes the error won't show. Edit your configuration.php and find the line starting with public $error_reporting and set it to:
public $error_reporting = 'development';

This instructs Joomla! to enable maximum error, warnings and notices verbosity. In 99.9% of cases it will result in the error messages being shown on the browser.

If you still get a white page, delete the php.ini files your created and choose a different host. If your host doesn't allow you to debug any PHP-related issues there is no point paying them.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

JosBlo
Nicholas,

thank you for your quick reply!

The website is build with the Gantry framework / Rockettheme, i found in their forums that this issue is not unknown. I haven't found a solution however ....

In the errorlog this message is very often seen:

PHP Fatal error: Class 'JModuleHelper' not found in /home/kynolo/public_html/libraries/gantry/core/renderers/gantrymodulesrenderer.class.php on line 60

Best regards, Jos

nicholas
Akeeba Staff
Manager
As you said, it's a known bug in the third party template framework Gantry. All I can tell you is that you should first try to upgrade Gantry and your template to their latest versions. If that doesn't help it would be a good idea to use a different template.

Please note that while transferring your site / restoring a backup does not alter the files in any way, just the fact that you are restoring to a different server (even if it was on the same host) means that your site is now running under a different server setup. It is fathomable that even a small configuration change can trigger a bug in third party software. The bug lies in third party software, not our. As a result it is impossible to us to offer support for third party software. In this case you must ask the third party software's developer for support, in your case RocketTheme. If they can't offer support you don't have much choice than to use something else: a different server where this software works or a different software which works on this server.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

JosBlo
Nicholas,

thank you. I will transfer a copy of the site to my Rochen VPS to see what happens. Thank you for you directions / instructions.

Best regards, Jos

nicholas
Akeeba Staff
Manager
You're welcome, Jos!

FWIW, we are hosted on a Rochen MVS (basically, a souped up VPS) and do use a Gantry-based template. To the best of my knowledge our site doesn't throw any Gantry-related errors. At least I haven't seen anything in the error logs or had any complaints so far.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!