Support

Admin Tools

#41403 Admintools blocks panopticon

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
5.2.2
PHP version
8.3.10
Admin Tools version
7.6.2

Latest post by nicholas on Tuesday, 03 December 2024 02:05 CST

pklinke

I had to restore a akeeba backup of my site. Since this restore (?) I think there was no more connection from panopticon.

After searching and trying around I now have added this setting in Admin Tools htaccess-maker:

 

Allow direct access to these files

/api/index.php/v1/panopticon/admintools/scans

 

Now it works again, but is it the right way?

 

Have a nice day

Peter

 

 

Sincerely

Peter

nicholas
Akeeba Staff
Manager

No, Admin Tools does not block Panopticon.

Adding /api/index.php/v1/panopticon/admintools/scans is wrong. There is no such file on your site. All API paths are SEF URLs. The “Allow direct access to these files” exceptions are for real, existing files on your site.

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!

pklinke

The fact is that panopticon could no longer connect until that.
Only when I added this path in Admintools the connection was possible again.

 Now I have removed this entry and it seems to still work. May be something was muddled.

crazy!

 

 

Sincerely

Peter

nicholas
Akeeba Staff
Manager

I really can't see how this happens. I know what kind of information is sent to the v1/panopticon/admintools/scans endpoint (either none, or the start point for paginated data), and that it can't be blocked by the .htaccess file. Regardless, I did create a test site with all .htaccess options enabled and still couldn't reproduce the problem you have.

Moreover, that endpoint is only involved in running the PHP File Change Scanner. It is not involved with connecting the site to Panopticon. The core and extensions information is pulled from two completely different endpoints. If those were blocked, the rule you added would have not made any practical difference.

I can't help but thinking that maybe you misdiagnosed the issue and whatever the root cause was stopped being the case around the time you added the .htaccess rule, essentially creating a placebo effect.

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!