Support

Please see https://forum.joomla.org/viewtopic.php?t=993760. I am attempting to update from Joomla v4.2.2 to v4.2.3 and seeing the same error. I noticed after I first saw the error that there are updates for both Akeeba Backup Pro and Admin Tools Pro, so I attempted to apply those updates. The update to Admin Tools went fine but the Akeeba Backup Pro update did not go well. I got a message that I should have copied down but instead tried again, hoping that things would be better the second time around. The update did work after that initial error (which I am very sorry not to have recorded). 

However, the Joomla update is still failing with the same error message reported by somebody else in the joomla forum referenced above (see attached screen shot). 

I'm not using mod_security2 (have no idea what it is). I haven't done anything to protect any files or directories that were not protected prior to the prior site update (upgrade from J4.2 to J4.2.2).

Nicholas - I am aware of all the things you wrote about in your reply, including that you'd developed the Joomla Update for J3 to J4 upgrades. That is why I thought you would be especially interested in the fact that some folks - I find it hard to believe that I and the poster of the topic at https://forum.joomla.org/viewtopic.php?t=993760 are the only two people who have encountered this issue while updated from J4.2.2 to J4.2.3. 

I should mention that of the five different sites I have checked (and which I inherited from somebody else) this one site that is giving me trouble is the only one that is using the Admin Tools generated .htaccess. I did not encounter any issue like this with the original update from J3.10.11 to J4.2.2 and I am absolutely sure that I did not modify the .htaccess file manually on this site.

I have examined the .htaccess file and I do not see 

I DO see this:Allow direct access to these files

but I do see this:

# Explicitly allow access to the site's index.php main entry point file
RewriteRule ^index.php(/.*){0,1}$ - [L]
# Explicitly allow access to the site's robots.txt file
RewriteRule ^robots.txt$ - [L]

I expect that I can add the line

RewriteRule ^administrator/components/com_joomlaupdate/extract.php^ -[L]

to fix my issue.

However, I am puzzled if not perplexed  - and I expect you are also - as to how I was able to perform the J3.10.11 to J4.2.2 upgrade without a problem if the .htaccess file did not have a rule allowing access to that extract.php file. I have a copy of the pre-update files and would be happy to send you the .htaccess file from that along with the current (somewhat different) .htaccess file from the J4.2.2 version of the site to further your investigation. Let me know if you are interested in seeing those or anything else that I might be able to do to help figure out what might have happened. Since the J4.2.3 update is relatively new, I suspect that you and/or the Joomla forum will receive more questions along these lines.

I apparently did not read your original reply to the ticket as carefully as I should have. I am an old-timey kind of guy who has been futzing around with .htaccess for a long time so I was thinking that was what I was supposed to do... After examining the generated .htaccess more closely, however, I can see that I would be way out of my depth in attempting to do that. Admin Tools clearly encapsulates orders of magnitude more expertise and person hours of experience than I have or would want to have. I have followed your instructions and everything is good now.

Thank you