Admin And Checkout Throw 500 Error

I'm running Zencart pretty vanilla at this point.

I had someone report that there were problems checking out. So I went into admin and was looking around. I think I made some minimal change and now I can't use admin anymore without 500 errors throwing.

My logs don't feel helpful, they reference a module I have and I removed the .php hoping that might fix things.

My host's cpanel shows a high load and some low space on some partitions but not 100% on either.

How do I troubleshoot? I can generate the 500 error anytime I try to check out and when I try to just go to the admin page but it's not really sending a log each time to look through.

What answer does your host have for you?

Quote:

---

Originally Posted by dbltoe

What answer does your host have for you?

---

I haven't heard back from them yet

If you're running Zen Cart 1.5.7 and your host updated PHP to a more recent version, it could certainly cause some 500 errors.

Check your PHP version.

https://docs.zen-cart.com/user/first_steps/version/

Quote:

---

Originally Posted by swguy

If you're running Zen Cart 1.5.7 and your host updated PHP to a more recent version, it could certainly cause some 500 errors.

Check your PHP version.

https://docs.zen-cart.com/user/first_steps/version/

---

I just went into MultiPHP Manager and forced 7.4 on my main domain and that didn't seem to help.

And also can't get into admin to see what versions of thing it's showing in there

I do notice each page that doesn't load says it's not secured like it couldn't load the cert but I don't think that is the problem but a symptom

In your cPanel's File Manager, take a look at your .htaccess.

It will be different numbers, but when cPanel forces a version of PHP, it should show in the .htaccess file.

This is one using 8.0. Yours may not have the leading "ea-"

Code:

---

# php -- BEGIN cPanel-generated handler, do not edit# Set the “ea-php80” package as the default “PHP” programming language.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php80 .php .php8 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

---

If you still have not heard from your host, I would leave. cPanel makes it easy.

Yep still haven't hear from my host, they are usually snappy.

Well I installed a fresh 2.0.1 in another path and copied my database and upgraded it from 1.5.7 to 2.0.1 via the installer. I have forced PHP 8.1 on the domain to make sure the PHP works (that is the highest version I see available on my site). I can get into my admin area no problem, but tried to go to checkout and have similar issues.

I did a third install with Sofaculus and didn't move any database information and made a $1 test item. I could check out fully but every page I submitted gave me a "this is insecure" popup. I can see my cert on each page installed and valid so really unsure of why it would be throwing errors like that. Maybe this is part of my problem?

Here is my test upgrade, migration page that throws an error
https://tolivealie.com/store2/index....ckout_shipping

And here is the Softaculus generated one with just a test item, it will let you go to this page without an error
https://tolivealie.com/store3/index....ckout_shipping
but if you were to create an account it would then throw this
Attachment 20785

I'm at a loss here now. I thought I would be able to rebuild.

Let me check the .htaccess when I move my PHP back to 7.4

Attachment 20786

Hmm this is super odd, maybe at the root of the problem. If the cert is good, why would this be insecure?

Attachment 20787

I did the built in demo and see the same thing happen there. This feels like this is at my hosts level.

If I'm running PHP 8.1 will this create this insecure error?

It has nothing to do with the PHP version.

Check includes/configure.php and be sure all the URL entries (HTTP_SERVER and HTTPS_SERVER) have values that start with "https://"

Quote:

---

Originally Posted by swguy

It has nothing to do with the PHP version.

Check includes/configure.php and be sure all the URL entries (HTTP_SERVER and HTTPS_SERVER) have values that start with "https://"

---

They do. And ENABLE_SSL is true. I haven't edited this file since 2020 either so no changes have been done there.

Attachment 20788

For the sake of continuity, this was the same on my reloaded 2.0.1 system (/store2) but not on the Softculuous install (/store3) and I fixed it there but that site is still acting the same.

You just keep adding possible failure points.

NEVER use any source for ZC than ZC's official location.

Quote:

---

Originally Posted by dbltoe

You just keep adding possible failure points.

NEVER use any source for ZC than ZC's official location.

---

The /store2 site is just that. I guess it was silly to not deploy again like that but wanted to spin one vanilla one up without my data again quickly since I forgot to test without my data in there intially.

Definitely nowhere closer to a solution yet.

Don't know whether I understood right but you can use subfolders for your different versions as you want.
As long you as you route each one of them to subdomains.

E.g.
example.com -> www.example.com
htdocs/shop1/ -> www.example.com
htdocs/shop2/ -> shop2.example.com

What is your URL?

Are you using a Control Panel?

Hey,

The problem is on checkout or upon going to my admin page I get a 500 error that dead stops being able to use the store for checkout or modifying the store.

I've done two different installations to see if I could get back up but both of them have the same issue so I think the problem is from my host at this point.

https://www.tolivealie.com/store (and /store2 and /store3 - store2 is fresh install with an imported and upgraded database and store3 was a Softaculous install with a test item).

My host does use CPanel and I have PHP 8.1 set on there to make sure it isn't a problem with either 1.5.7 or 2.0.1.

I just put it in mantaince mode, found the configure table where I could set that so /store won't load now

Now I feel totally crazy. Brand new hosting and I rebuild my store and same problem

Attachment 20789

Attachment 20790

I did another fresh install and forced PHP 8.3 and got a clean checkout.

There must be something in my database that happened in the last week that has fubared things? Is that possible?

Do you have a shipping module that is dependent on PHP 8.3?
Also with your new hoster have you verified that logs are created?

Quote:

---

Originally Posted by swguy

Do you have a shipping module that is dependent on PHP 8.3?
Also with your new hoster have you verified that logs are created?

---

You know I haven't tried taking out the shipping module to test that. I use the USPS one that lat9 writes and I updated it a few months ago. Not being able to get into the admin on my original site makes a lot of this complicated.

New host is I just signed up for a year of Godaddy hosting at the lowest level, not sure the logs I'd be asking them about.

Taking out usps.php didn't help.

Keeps feeling like the problem is on both hosts when I go to submit when its not HTTP it shows insecure errors each time I have to click but on HTTPS it shows a 500 error. SSL cert is clearly in place, I have changed HTTPS in both those fields, and I have SSL turned on in configure.php. Not sure how much more I can do and it is super frustrating that I'm not up with the new host.

Attachment 20791

I moved a 1.5.7 install directory in to see if it showed anything and it shows me these, would either break the store?

Okay I deleted all the denies out of my .htaccess file and that seemed to let me checkout.

How that was the problem or why that followed to the brand new store on a new host I have zero clue.

Still can't get into admin but will keep working.

Any ideas on how to fix my /admin folder (obviously named a weird name)? Moving the .htaccess to the that folder doesn't help that load at all.

I also did a test order to myself and got the payment email but nothing from the store.

Quote:

---

Originally Posted by wcbutler

I also did a test order to myself and got the payment email but nothing from the store.

---

Disregard, it came through just a whole lot later. Need to figure out why my admin isn't working still.

<RANT>

I would be willing to bet that your "bottom line" hosting with GoneDaddy involved paying for three years at a time. Their great-looking $5.99 offer is only available with a 3-year contract. Otherwise, it starts at $11.99 for a month. And, monthly gets nothing free. Get ready for the "Oh you want to have a ##########__ (Insert some feature here)."

I hope you bothered to look at the fine print. Let's take the annual plan. What a bargain at $6.99 (actually, you have to pay $83.88 up front). You get two email addresses but they are only free for three months.

You get a free SSL but it is not free after the first year. That's going to be an extra $99.99 a year.

You get free Website Security until December of this year when the trial period is over and, unless you can find some way to deny it, you will automatically be renewed at the $158.88 fee.

As a minimum (with email being $1.99 a month for two addresses after two months), your first year will actually be $262.66 and the second will be $366.63.

And most sites need/use abuse@, sales@, info@, and postmaster@ not to mention emails for the owner(s) and staff. Every 2 address is another $1.99 a month.

Your first year is going to cost you a minimum of $21.89 per month on an annual plan and the second will be $30.55 per month. You will not be hit with most of that until December (right after the 30-day return date) But, you will have to pay both in a lump sum for year two.

And, they won't give you enough heads up on the renewal to transfer your domain if you are unhappy. They will probably want to keep your credit card on file so they can bill you in the middle of the night.

And, you will be unhappy within 6 months or less. They keep you at bay with problems till just after the 30-day mark and suddenly defer you to everybody else as the source of your problem.

Their "sorry about that" return policy will probably result in you paying $200+ for six months. It's a great business plan that keeps them afloat quite well.

I wonder why they are not listed as a Zen Cart Certified Host?

</RANT>

I just signed up quickly to try to get closer to a solution. I'm way closer on my original host to a solution so I just need this one thing figured out.

The odd thing is restoring my old admin didn't fix anything. I've tried to put the same working .htaccess from my /store into /store/admin but it just either spins forever or gives me a 500 error there. What is weird is it was working when my store wasn't before and just hung up and broke at some point during my troubleshooting (not during any major change either)

Another note, I've been running things with my current host since ZC 1.3.8 which looks like it was released 14 years ago. Again never had no responses from them, but it I can get back up under them then I'm happy.

Update - I'm making progress rebuilding on 2.0.1 with an imported DB.

Moved .htaccess in. Had to do the trick I found here to set the country in Paypal to US in paypadp.php or whatever then remove the paypal module, remove that piece of code, and reinstall the Paypal module. I had to re download and put into place the USPS shipping module.

Pulled my template in, edit the metadata file, index file, and header (my header is a bit different).

Now the last things to fix are for some reason on product pages with my old template, images on product pages show full size above the small image below. I expected there to be some templating changes needed going from 1.5.x to 2.0x. so I guess that is the last part I need to fix.

Still not even sure why my .htaccess from 4 years ago messed things up and then could not for the life of me get the old /admin working even from backups.

I guess I'm mostly good and I appreciate all your help. Never had to do that level of work on ZC other than the templating I did in 2009 where I had to learn how to do that. Will be a sigh of relief when I get this last image problem fixed and I already took a snap of the store where I'm at.

Attachment 20792

FYI this is the image problem at this point. Again old templating/CSS issue somewhere.

Copied stylesheet_image_modals.css and stylesheet_image_modals.php into my template and that fixed that! Thanks for having my freak out on here and helping me. Still so confused why I needed to do all this.