Support

Admin Tools

#31862 Locked out after directory change

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 on Wednesday, 13 November 2019 17:17 CST

sirpentium2
Greetings,

I built a Joomla site in a directory named "stan1" (synapsystemsinc.com/stan1).
Once the site is complete and ready to go live I moved everything from the stan1 directory into the http directory to make it live and the site works well except I can no longer sign in to Akeeba, I am locked out.

I then moved the site back into the stan1 directory and I can sign into Akeeba again. Seems when I move it from the stan1 directory to the http directory, although the site works great I can not get into Akeeba.

Thoughts?

dlb
I'm a little confused by "log into Akeeba". I assume you mean you can't log into the Joomla Admin area.

Let's delete the .htaccess file in the root of the live site, then copy htaccess.txt to .htaccess. Can you get in now?

If you can, just go to .htaccess Maker, update the two URLs at the bottom of the page and regenerate your .htaccess file.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

sirpentium2
Hi Dale,

Correct, I cannot get to the Joomla log in page. Just to confirm, playing it safe:

1. delete the current .htaccess file
2. create a new empty .htaccess file and type in only "htaccess.txt" no quotes.
3. sign in, if I can sign in then:
4. go to htaccess maker and update the 2 urs and the bottom of the page and regenerate the .htaccess file

Correct?

Thanks,
Bob

dlb
Almost. I wasn't clear enough.

htaccess.txt is a file in the root of your site. It is Joomla's default .htaccess file that we use as a "known good" file. Just copy the contents out of that file into your .htaccess file.

I should have asked you - what happens when you try to log in?


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

sirpentium2
OK, now I think I got you. I will put the original Joomla htaccess file in place of the current one. be back soon.

Thanks

sirpentium2
Ok, I deleted the .htaccess file on the server. I replaced it with the original .htaccess file from the Joomla package so the .htaccess file is now the original prior to installing Akeeba tools.

I try to sign in but still cannot sign in. When I go to synapsystemsinc.com/administrator I still get the same issue, can't get to Joomla admin sign in. see attached htaccess currently in place and the same sign in dia box.

sirpentium2
Won't let me upload the htaccess so I added a .txt etension to get it to upload

sirpentium2
##
# @package Joomla
# @copyright Copyright (C) 2005 - 2019 Open Source Matters. All rights reserved.
# @license GNU General Public License version 2 or later; see LICENSE.txt
##

##
# READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE!
#
# The line 'Options +FollowSymLinks' may cause problems with some server configurations.
# It is required for the use of mod_rewrite, but it may have already been set by your
# server administrator in a way that disallows changing it in this .htaccess file.
# If using it causes your site to produce an error, comment it out (add # to the
# beginning of the line), reload your site in your browser and test your sef urls. If
# they work, then it has been set by your server administrator and you do not need to
# set it here.
##

## No directory listings
<IfModule autoindex>
IndexIgnore *
</IfModule>

## Suppress mime type detection in browsers for unknown types
<IfModule mod_headers.c>
Header always set X-Content-Type-Options "nosniff"
</IfModule>

## Can be commented out if causes errors, see notes above.
Options +FollowSymlinks
Options -Indexes

## Mod_rewrite in use.

RewriteEngine On

## Begin - Rewrite rules to block out some common exploits.
# If you experience problems on your site then comment out the operations listed
# below by adding a # to the beginning of the line.
# This attempts to block the most common type of exploit `attempts` on Joomla!
#
# Block any script trying to base64_encode data within the URL.
RewriteCond %{QUERY_STRING} base64_encode[^(]*\([^)]*\) [OR]
# Block any script that includes a <script> tag in URL.
RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
# Block any script trying to set a PHP GLOBALS variable via URL.
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\[0-9A-Z]{0,2}) [OR]
# Block any script trying to modify a _REQUEST variable via URL.
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\[0-9A-Z]{0,2})
# Return 403 Forbidden header and show the content of the root home page
RewriteRule .* index.php [F]
#
## End - Rewrite rules to block out some common exploits.

## Begin - Custom redirects
#
# If you need to redirect some pages, or set a canonical non-www to
# www redirect (or vice versa), place that code here. Ensure those
# redirects use the correct RewriteRule syntax and the [R=301,L] flags.
#
## End - Custom redirects

##
# Uncomment the following line if your webserver's URL
# is not directly related to physical file paths.
Cannot upload so here is the content

# Update Your Joomla! Directory (just / for root).
##

# RewriteBase /

## Begin - Joomla! core SEF Section.
#
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
#
# If the requested path and file is not /index.php and the request
# has not already been internally rewritten to the index.php script
RewriteCond %{REQUEST_URI} !^/index\.php
# and the requested path and file doesn't directly match a physical file
RewriteCond %{REQUEST_FILENAME} !-f
# and the requested path and file doesn't directly match a physical folder
RewriteCond %{REQUEST_FILENAME} !-d
# internally rewrite the request to the index.php script
RewriteRule .* index.php [L]
#
## End - Joomla! core SEF Section.

dlb
Ah ha! (The screen shot did it.)

The problem is the .htaccess file in the /administrator folder. It does not travel well. Just delete it so you can log in. (The one in the /administrator folder, not the root.)

When you get back into the back end, you can regenerate your .htaccess file in .htaccess Maker and re-enable Password Protect Administrator to generate the .htaccess and .htpasswd files in the /administrator folder.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

sirpentium2
Hi Dale,

Cool, that worked and I can now sign in. Not quite sure how to regenerate the htaccess for the admin and restore the Akeeba password dia.

Thoughts? directions?

Thanks you got me in.

Bob

sirpentium2
Hi again Dale,

I got it all working as it should. A BIG THANK YOU. You were/are a great help.


Thanks again,
Bob

dlb
You're welcome!


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!