Problem with admin password

[Ironside]

Okay, I've got myself into a bit of a pickle I'm starting to panic now. I'm planning on upgrading a 2.5 website to 3.4. So what I did was to use Akeeba to make a clone of the website. Then I put this cloned website onto a test domain. However, I cannot for the life of me get the password to work. I changed it several times in PHPmyadmin > users. In the password field I chose MD from the drop-down and re-entered my desired password. Like I say, I've tried it several times and it just will not work. Can anyone shed some light on what is going on.

[toivo]

This tutorial should help:
https://docs.joomla.org/How_do_you_reco ... assword%3F

[Ironside]

This is seriously starting to irritate me. I had problems with two websites. Eventually I got the main website to work properly by changing the password in PHP my admin. Now I'm on another computer that password doesn't seem to be working. So I've been attempting to change it again with no luck. Just wondering whether it will take a few minutes. I have taken a copy of this website using Akeeba and put it on another test domain. Again, I couldn't get the password or username to login. So been trying to change alarm at having any luck there. Just don't know what's happening

[Webdongle]

When you run ANGIE ... on the 'Site setup' page ... 'Super User settings' ...
What super is selected ?
and
Do you leave both the 'Password' & 'Password (repeat)' fields empty or fill both fields in ?

[Ironside]

Okay, completely stuffed at the moment. Not only am I as admin not able to login the back end for the front end, but it seems that none of my members can either. I simply don't know what I've done.

I better explain exactly what I did yesterday, maybe someone has done the same thing and knows how to solve this frustrating problem

Okay, I'm running 2.5 .28 on Oscarfishlover.com. I want to upgrade to the latest version of Joomla!, however after the last time I tried I messed the database up. So this time I decided to try the upgrade on a test domain first using a clone of the website. Now I'm using the Go Geek hosting package with site ground. My main domain is tetraplegic living.com. So I decided to create a sub domain and call it "test" the installation went without flaw, Akeeba seem to do as I asked. Now with the benefit of hindsight I think it's got something to do with the configurations file. I don't see how the to them can be interacting or clashing with each other because they are on different domains. I've tried resetting my password in the database but that made no difference.

If anyone can shed some light on why I'm not able to login front or back end I would be very grateful

[Webdongle]

You are installing the copy to a separate database ... yes ?

Try https://www.apachefriends.org/index.html (or Mamp if you have a MAC) and use the jpa file to create a copy of your site on localhost.

[Ironside]

Everything is going my way now. It turned out to be my fault with the password, I had disabled the Joomla!_user plug-in because I was having problems with the Akeeba backup not finishing properly. After uninstalling it and then reinstalling it Akeeba is working fine now. I've got a spare domain that I'm going to use for testing, so I'm just going to upload the JPA file and use kickstart to open the website on this domain. This way I can do all the testing I may need to do and if it all goes wrong then I have not damaged a live and very important website.

I've got 2 websites that are still using the 2.5 platform. It just happens that these are my main websites and I really can't afford to have anything go wrong. I did try and update one of them a couple of weeks ago and everything seemed to be going really well when I was running the update from 2.5 up to 3.4, but then something went wrong and the database was corrupted.

I've now moved hosts are much happier where I am. I'm confident that I can perform this upgrade without encountering any more problems. Anyway, it's quite good that some of these things have happened, you don't learn without having things go wrong.