HTTP ERROR 500 on 'Create New Client' + Willy Wonka

JITS

A-yup.

Edit

Just for giggles and spit, let's see what a very minor edit to the script does for the outcome. Since @aftechro stated up there he's using Ubuntu 20.04 LTS:

aftechro

JITS i did the manual install, not the script, but yeah, was not paying attention when you said the script install :d

JITS

Ugh…

JITS

Okay, that up ^-- was fixed with a crappy old apache2 ".conf" file. That's on me.

And now … after all of that hard work, multiple experts (yeah, that's right - YOU two, @aftechro and @johnny), on the final step that normally gave me the HTTP ERROR 500, I got … this:

YAY!!!

So, now I (and you guys) know a few things…

It will work on Debian 11
It works with the (L)AMP stack as follows: Apache 2.4.59, MySQL 15.1\MariaDB 10.5.23, PHP 7.4.33
It's probably a very good idea to include the whois into the install script; I don't know if it helped, but everything is working now, so…

Everyone's observation of events was instrumental. I'm very happy with things so far (it is, after all, the beginning). Thank you, muchly. Very muchly.

wrongecho

Hey there!

A little late to the party, but glad you got it working!

Both the manual install steps and the install script call for the whois package so I'm struggling to understand exactly what the root cause of the issue was..

If you do end up replicating this issue again, please share the relevant PHP/Apache error logs (500 errors should log something presumably) so we can dig a little further.

Bigbug

wrongecho I had this kind of problem with cron on my production server, after installation everything was working except any of the cron jobs, when I dropped to shell and executed sudo crontab -l it told me it couldn't find such a package, it turned out that cron wasn't installed out of the box (I use a Debian 12 VPS from OVH cloud)

I think it would be helpful to add cron in the list of install_packages() on line 43

I also saw that the last function print_final_instructions() on line 115 isn't actually used to print final instructions and could be removed

🙏

aftechro

Happy days!

Personally, I’m not a big fan of Apache—I prefer NGINX 😄, but that's just my preference.

For troubleshooting in the future, always remember to check the /var/log/syslog and PHP logs. They’ll contain the error messages you need, making it much easier to figure out what needs fixing.

johnny

Hey @Bigbug Your right I noticed that too some VPS's exclude cron package for some reason. Ill add it to the package install script just in case and remove the print final instructions

psion13

Hi all, this exact scenario appears to be happening to me! I was able to create 2 clients then discovered when testing mail configs that cron wasn't running and got that activated, emails working!

Then when I went back to add more clients I started getting:

This page isn’t working

domain.domain.tld is currently unable to handle this request.

HTTP ERROR 500

I am using LAMP stack on Ubuntu 22.04.4, is this something I can resolve with the current setup or do I need to switch to Debian?

Bigbug

psion13 I'd recommend to switch to Debian 12 if you haven't entered any much data
as there is some upstream issues with php packages on ubuntu and it's not seamless

with Debian 12 you shouldn't have any of these problems (from my experience)

🙏

JosephWithCOR

The only issue would be Debian 11 doesn't support php8.x and the composer doesn't won't work properly with php<=8.x

https://forum.itflow.org/d/926-composer-dependencies-require-a-php-version-820

https://forum.itflow.org/d/950-composer-detected-issues-in-your-platform/14

https://forum.itflow.org/d/987-parsing-stopped-working-randomly/4

Bigbug

JosephWithCOR I should've mention 12

I edited my post

« Previous Page