Support

Admin Tools

#13176 Site IP Blacklist

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, 06 August 2012 14:30 CDT

kush
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
Joomla! version: 2.5.6
PHP version: 5.3.10
MySQL version: 14.14 Distrib 5.5.24
Host: Rackspace
Admin Tools version: 2.3.1

Description of my issue:

I'm having trouble with a banned user not receiving the proper 403 response when trying to access my site. Instead of the 403, my site outputs some errors. Note, this probably has something to do with me using nginx as my web server, as I tried this out on a fresh install of Joomla 2.5 on my local computer (MAMP) and it works just fine. Just wondering if I can get some ideas on what might be going wrong.

I tested it by adding my own IP address to the black list and then setting "Disallow site access to IPs in Blacklist" to "yes". After I save, the administrator screen goes blank and the following text is displayed: "You've got to ask yourself one question: Do I feel lucky?"

I assume that means that it is working correctly. However, when I navigate to my main site (not administrator), I get the following output:

jos-Warning: JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING

JSite -> initialise() @ /home/site/www/public/index.php:30
JApplication -> initialise() @ /home/site/www/public/includes/application.php:116
JApplication -> triggerEvent() @ /home/site/www/public/libraries/joomla/application/application.php:230
JDispatcher -> trigger() @ /home/site/www/public/libraries/joomla/application/application.php:642
JEvent -> update() @ /home/site/www/public/libraries/joomla/event/dispatcher.php:161
call_user_func_array() @ /home/site/www/public/libraries/joomla/event/event.php:71
plgSystemAdmintoolsPro -> onAfterInitialise()
plgSystemAdmintoolsPro -> IPFiltering() @ /home/site/www/public/plugins/system/admintools/admintools/pro.php:88
JError :: raiseError() @ /home/site/www/public/plugins/system/admintools/admintools/pro.php:498
JError :: raise() @ /home/site/www/public/libraries/joomla/error/error.php:251
JError :: throwError() @ /home/site/www/public/libraries/joomla/error/error.php:176
call_user_func_array() @ /home/site/www/public/libraries/joomla/error/error.php:214
JError :: handleCallback()
call_user_func() @ /home/site/www/public/libraries/joomla/error/error.php:765
plgSystemRedirect :: handleError()
JError :: customErrorPage() @ /home/site/www/public/plugins/system/redirect/redirect.php:109
JDocumentError -> render() @ /home/site/www/public/libraries/joomla/error/error.php:798
JDocumentError -> _loadTemplate() @ /home/site/www/public/libraries/joomla/document/error/error.php:107
require_once() @ /home/site/www/public/libraries/joomla/document/error/error.php:135
JSite -> getParams() @ /home/site/www/public/templates/lbc/error.php:13
JComponentHelper :: getParams() @ /home/site/www/public/includes/application.php:358
JComponentHelper :: getComponent() @ /home/site/www/public/libraries/joomla/application/component/helper.php:92
JComponentHelper :: _load() @ /home/site/www/public/libraries/joomla/application/component/helper.php:43
JError :: raiseWarning() @ /home/site/www/public/libraries/joomla/application/component/helper.php:415
JError :: raise() @ /home/site/www/public/libraries/joomla/error/error.php:276

Any ideas? Thanks.

nicholas
Akeeba Staff
Manager
You seem to be using NginX in reverse proxy mode. In this case, Apache needs an extra module so that it reports the real IP (not the internal network IP, as it does right now) to PHP.

Regarding the other error message, it seems to be related to your template, namely its error.php file, as shown in this message:
JSite -> getParams() @ /home/site/www/public/templates/lbc/error.php:13
It seems to be trying to load some component's parameters, only that the specified component does not exist and throws the error you are seeing.

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!

kush
Thanks for the tip on the error message for error.php, I missed that. That was causing the problem, as it works as expected now that I changed the line in error.php (I'm not using nginx in reverse proxy mode either, btw).

So that works, but I normally use Qlue Custom 404 (http://extensions.joomla.org/extensions/site-management/error-pages/16481) enabled so that Joomla can handle and log all of my errors (403, 404, 500). I had disabled it before I posted this ticket as I thought it may have been what was causing the error. Now that I fixed the error in my error.php, Admin Tools displays the 403 message properly, provided I have Qlue disabled. But, when I have it enabled, I get this when viewing the site from the front end from a banned IP address:

jos-Warning: JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING

JSite -> initialise() @ /home/site/www/public/index.php:30
JApplication -> initialise() @ /home/site/www/public/includes/application.php:116
JApplication -> triggerEvent() @ /home/site/www/public/libraries/joomla/application/application.php:230
JDispatcher -> trigger() @ /home/site/www/public/libraries/joomla/application/application.php:642
JEvent -> update() @ /home/site/www/public/libraries/joomla/event/dispatcher.php:161
call_user_func_array() @ /home/site/www/public/libraries/joomla/event/event.php:71
plgSystemAdmintoolsPro -> onAfterInitialise()
plgSystemAdmintoolsPro -> IPFiltering() @ /home/site/www/public/plugins/system/admintools/admintools/pro.php:88
JError :: raiseError() @ /home/site/www/public/plugins/system/admintools/admintools/pro.php:498
JError :: raise() @ /home/site/www/public/libraries/joomla/error/error.php:251
JError :: throwError() @ /home/site/www/public/libraries/joomla/error/error.php:176
call_user_func_array() @ /home/site/www/public/libraries/joomla/error/error.php:214
JError :: handleCallback()
call_user_func() @ /home/site/www/public/libraries/joomla/error/error.php:765
plgSystemQlue404 :: handleError()
plgSystemQlue404 :: _renderComponent() @ /home/site/www/public/plugins/system/qlue404/qlue404.php:287
require_once() @ /home/site/www/public/plugins/system/qlue404/qlue404.php:344
JController -> execute() @ /home/site/www/public/components/com_qlue404/qlue404.php:28
Qlue404Controller -> display() @ /home/site/www/public/libraries/joomla/application/component/controller.php:760
JController -> display() @ /home/site/www/public/components/com_qlue404/controller.php:19
Qlue404ViewQlue404 -> display() @ /home/site/www/public/libraries/joomla/application/component/controller.php:721
JView -> get() @ /home/site/www/public/components/com_qlue404/views/qlue404/view.html.php:51
Qlue404ModelQlue404 -> getItem() @ /home/site/www/public/libraries/joomla/application/component/view.php:386
JModel -> getState() @ /home/site/www/public/components/com_qlue404/models/qlue404.php:41
Qlue404ModelQlue404 -> populateState() @ /home/site/www/public/libraries/joomla/application/component/model.php:400
JSite -> getParams() @ /home/site/www/public/components/com_qlue404/models/qlue404.php:16
JComponentHelper :: getParams() @ /home/site/www/public/includes/application.php:358
JComponentHelper :: getComponent() @ /home/site/www/public/libraries/joomla/application/component/helper.php:92
JComponentHelper :: _load() @ /home/site/www/public/libraries/joomla/application/component/helper.php:43
JError :: raiseWarning() @ /home/site/www/public/libraries/joomla/application/component/helper.php:415
JError :: raise() @ /home/site/www/public/libraries/joomla/error/error.php:276

Perhaps it's not possible for me to use this feature in Admin Tools if I am going to use Qlue 404? I don't fully understand the output, but perhaps Qlue can't be loaded since the IP address is banned? It would be cool if I could figure out a way to make it work. I appreciate any ideas. Thanks.

nicholas
Akeeba Staff
Manager
As you can see in the trace log, the error is generated in the Qlue component, namely components/com_qlue404/models/qlue404.php at line 16. I am not the author of that extension, therefore I can not provide support for it. Please contact its developer and please give them the same trace log you gave me here so that they can identify the source of the issue.

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!

kush
Understandable. Unfortunately, their support is not nearly as great as yours is (in that I get no reply). I'll figure something out. Thanks.

nicholas
Akeeba Staff
Manager
Seeing the error message, I can make an educated guess. Please take this advice with a pinch of salt; I've never used Qlue and I do not have a clue how it works (pun not intended). I suspect that you get this error because something is not properly installed on your site. Most likely installing Qlue again would fix this error.

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!