Upgraded from 3.0.3.8 to 4.0.2.3 and now have admin password match errors.

(Originally posted in the V3 forum in error.)

Upgraded from 3.0.3.8 to 4.0.2.3 and now have admin password match errors.
(Default theme, no extensions, no additional translations.)

The upgrade didn't go at all well until I discovered that the storage directory, which was in a private folder, has now got to be in the system/storage path. Once I fixed that, by moving the files and altering config.php in the main and admin folders, I could see the admin login page and the store in maintenance mode where Ieft it.

The problem is that admin login credentials are not recognized "No username or password match."

I've experienced the "timezone proble"m before and it is currently "UTC" in the system/config/default.php file. The store was UTC-6 DST and I don't recall how to reset it.

Time Zone may or may not be the problem. Any suggestions on which logs to submit or corrective action?

Last time I had the time zone problem (2018) I modified system/framework.php but it made no difference with V4. Still locked out.

Giving up on OC4 for now.

Motivation for upgrading to OC4 is that 3.0.8 won't pass a PCI scan due to outdated jQuery. But OC4 broke the store so for now I'm rolling back to 3.0.8. IF OC required storage to not be in the OC root due to insecurity why in the heck did it change with 4.0? Pun intended but I think this is the "root" of the problem and my config.php files which moved it must have broken the 4.0 install.

Too many problems with this release...

I did a bare metal install with an "empty" test db and OC 4 installed flawlessly.
My conclusion thus far is that when the initial upgrade was done the config.php files specified storage in a private folder above the OC root.
Moving the storage files to inside OC and changing the storage path back to the default allowed it to install with an empty dbf.
I can login as admin to an empty store and the first warning I get is to move the storage to a protected folder. I also see a default demo storefront.

The question now becomes will it upgrade the working OC3 db correctly with the storage path in OC's folder.
I'll be mirroring the live db into the test db.
Apparently, with config.php initially being outside OC's folder, something didn't completely update in the db.

It's obvious that I'm completely on my own here and talking to myself...

So I took the working bare metal OC4 install and had the OC3 working db copied into the test db. I then ran install and it launched the upgrade script and reported a successful upgrade. Presumably the db was updated.

Was it really successful? No. Still can't login as admin with username and password failing to be recognized. The store front will display the top header categories, store logo etc. so the dbf is being read. This is getting beyond ridiculous. The $44 per month penalty for not being PCI-compliant is starting to look like a bargain compared to the intense wasted effort trying to upgrade to OC4.

I'm also super-impressed by the community support. I can't tell you how good it feels to be left hanging in the wind with this issue. Thanks everyone for your numerous suggestions. Looks like the time has come to find a new vendor. I need something that works and is upgradeable.

I am thinking of doing the same thing upgrading from 3.0.3.8 to 4.0.2.3 is it doable?

I think I found an answer to both my original and your question here: https://webocreation.com/how-to-upgrade ... ions-of-4/

We started upgrading some of our clients to Opencart 4.0.2.2 from Opencart 3.0.3.8. Here are the steps that we follow and some of the issues that we face and their solution to fix the issue.

Admin login issue
Now we tried to go to the admin section. We were not able to log in with the old username and password, so we have to insert the username and password from SQL. Here is the SQL that we use:

Code: Select all

INSERT INTO `oc_user` (`user_group_id`,`username`,`password`,`firstname`,`lastname`,`email`,`image`,`code`,`ip`,`status`,`date_added`) VALUES (1,'admin','$2y$10$3Tofs9U7zGWhbQ67l7uageuxOjo6zU88pRESFZaxY.D3Ms4RSSIAu','John','Doe','youremail@gmail.com','','','::1',1,'2022-06-04 11:39:23');

With the run of the above query, now you can log in with username: admin and password: admin123. After you logged in you can remove the /install folder, set the new storage folder, and rename the admin folder to your desired name.

I eventually gave up on 4.X and installed the 3.0.3.8 maintenance release to solve the requirement to run jQuery 3.7. That effort was also not without pain but after getting it going it now passes a PCI compliance scan.

If I had found the article earlier I might be running OC4 now.

Hi folks, I fixed my inability to log into OC4.0.2.3 admin once I upgraded the site to ssl, simply by changing http to https in the config.php file
define('HTTP_SERVER', 'https://your_domain/maintenance/');
I was getting a 'success' message through json (in dev view), but it would never go to the dashboard. The above change worked for me.
Hope it helps you...

have you solved this issue please? I upgraded 3.0.2 to 4.1.0 and cant login admin

sansou wrote: ↑

Wed Feb 12, 2025 6:02 pm

have you solved this issue please? I upgraded 3.0.2 to 4.1.0 and cant login admin

You will need to reset the password or import the parts of the passwords from your old database.
https://github.com/opencart/opencart/issues/14416