https 404:page not found after installing Magic SEO and PHP 5.3 on GoDaddy

I'm getting a 404 page not found for my admin and customer log in, I recently changed the php version to 5.3 to install Inveo magic seo. It was working fine for about 3 weeks, until I got a ssl error yesterday. I called godaddy, they "FIX" it, but now im getting 404 page not found. Please help me :shocking:

I am getting HTTP 404 Not Found error when click some links on my site. What can I do?

Please make sure www/.htaccess file content has been generated during the installation, mod_rewrite is loaded into Apache and www/.htaccess file handling is enabled. If you are running nginx web server, please make sure you've followed the instructions in www/.htnginx file.

I created a new htaccess file, but it is not generate the content.

Please provide a URL to your site.

http://www.firemagicparts.com/

GoDaddy probably wasn't aware of the rewrites from your SEO add-on. For myself, I don't use those anymore since it's not necessary and in my experience tends to break more things than it fixes. Perhaps someone can chime in with experience with that add-on. In the meantime, you could try renaming you htaccess file and see if the site works without it!? Just to see...

No promises, but I will try to keep it short...

My dedicated server was compromised so I ended up having it wiped and now reinstalling Zen Cart (original v1.5.1) from backups 30 days prior to the compromised event. After a couple of glitches (I forgot I added a mod AFTER the backup date) I can now visit the site just fine (Missing some images, but that's easy to fix).

The PROBLEM is trying to log into Admin! I am getting the following error:

Not Found
The requested URL /renamed-admin/login.php was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

The URL path DOES exist along with the file, login.php. I pretty much tried everything I knew, checked logs, disabled Magic SEO URL's, etc. Same problem.

Since the server was compromised on another domain on the server, to be safe I had changed the account login (changes path), changed the db_name and credentials, and made sure both configure.php files (catalog & admin) were updated with the changes as appropriate.

I also searched the database and updated any file paths that may have been stored in the db to the new and correct path(s).

I even tried adding a second admin via phpmyadmin with some SQL statements (similar to when you need to reset admin because of forgotten password). No help. (I did not delete and re-add the "Renamed-Admin" account, however.)

What else changed due to the rebuild besides the account name for the domain and db_name, db_database, db_password? Well, the dedicated IP changed and I requested a new SSL cert and installed it.

I am stumped and posting here as a last resort. What have I missed or overlooked? I searched the forum pretty good, but nothing is popping out at me as an "Ah ha!" moment...

Oh, because of the rebuild, I remember the ISP/Host provider said it would get the latest builds for the OS and so forth (CentOS). Using DirectAdmin (control panel) also states it has the latest versions of LAMP too (but not bleeding edge... lol).

Any ideas?

Have you checked file permissions (and selinux permissions if enabled) based upon your new hosting environments requirements?

This might be a stupid question, but is your SSL up and going? I was having the same problem with the admin page not showing, and it was an SSL issue.

Sorry for slow response... Day job and last night was busy.

@ride22 - Yes, SSL is working, as I checked that too by clicking on the "Lock" symbol in the URL address bar. All info came up correct, was green, etc.

@lhungil - Since SSL appears to be working correctly, don't think it's a file permission issue with the cert on the server. But I could be wrong...?

Any other ideas? Anybody?

FIXED IT! Thanks to @lhungil and @ride22 for their suggestions which got me to remember that SSL requires the use of "private_html". Duh! (I was in a rush to restore the site and simply forgot about that.)

So I searched the forum on my server's admin panel and found what and where I needed to make the change as I couldn't remember exactly where:

User Level Login in Directadmin -> Domain Setup/Administration -> Click on desired domain -> Check "Use a symbolic link from private_html to public_html - allows for same data in http and https" -> Save

Life is good once again. Whew!