My server been having issues since 1.8.12

Community Support
1

My friend originally set up my server, but after it automatically updated to version 1.8.12, I started experiencing issues. Now, I have to restart Apache and PHP 7.3 every 40 minutes to keep my site running; otherwise, I get an “Internal Server Error” with Error Code 500, displaying the message: “Oops! Something went wrong. The server encountered an internal error or misconfiguration and was unable to complete your request.”

My friend suggested that I might need to reinstall HestiaCP, but I’m wondering if there’s another way to resolve this. Can someone help?

1 Like
2

uh there was an issue with the PHP repository about a year ago. I know I had SOME issues about that time, but I finally got that sorted out (for the most part).

TECHNICALLY, I show that there are 2 different lists of Php Available.
Under Site, Advanced, I CAN select Php 8.3.

Under the WORDPRESS quick install, I am NOT able to select php 8.3.

I don’t know if that is ACTUALLY reflective of an issue. But yeah. I’d look for the Yuri Repo fix and make sure that it’s not biting you.

3

Config file Wordpress Quick install is outdated will get updated in 1.9

4

Check your log files why It is causing this issue

1.8.12 did not change anything regarding php it self…

5

If your nginx conf is using 1024 worker connections, try to raise it to 2048:.

sed -i 's/worker_connections 1024/worker_connections 2048/' /etc/nginx/nginx.conf
systemctl restart nginx
6

Thanks so much. I did a REALLY poor job on ‘fixing’ the yuri patch problem. But my server’s been 98% rock solid and stable, so I’m really happy how things have worked out.

I just need to write some sort of ‘Watchdog’ script and if I can’t connect to mySQL on 3-5 straight attempts, then reboot the server. I don’t want this to happen EVERY time EVERY 3-5 minutes.

So I think it just needs to extend the time each time it reboots the server.

7

I changed it to 2048, but it’s still not working. I’ve noticed I have to keep restarting Apache and PHP 7.4 every 30 minutes, and I’m not sure what’s causing the issue.

8

Question, if you change the worker connections do you need to change the ulimits?

9

Usually you should have enough limits for max processes and max open files but you can check it easily querying the limits of one of the running nginx worker processes:

cat /proc/"$(ps -ef | grep '^www.*[n]ginx.*worker proc' | tail -n1 | cut -d ' ' -f2)"/limits