Version 1.9.2 - initial test - bug report

Hi Team, I upgraded the server to 1.9.2 now. It solved most of the issues.
I have seen an issue on my server. I don’t know if this is the case with others.

I edited the web server configuration using the web UI 0n example.com:8083/edit/server/ → web server.
I use multi PHP. Php v 8.3 was the default. I installed 8.4 and changed the system’s PHP version to 8.4 using the drop-down.

All of a sudden all my sites were throwing 500 server errors. I checked the services in the UI. Php-fpm 8.3 service was disabled. I tried to start it but it didn’t start.

Now I switched back the system PHP version to 8.3. and started the php-fpm 8.3 service using the UI. It started and the sites are back online.
Now I went inside the WordPress panel to check the system status. To my surprise, PHP 8.4 was being used. Even though I have 8.3 selected it is still using version 8.4. I can confirm that. I checked the services, PHP 8.4 fpm is utilizing the CPU not 8.3.

Can you look into it? I don’t know if this is the case with the others.

Thanks!

Here are the screenshots to explain it better

Hope this helps

I have the same problem, I changed to php 8.3 and solved the error of the (wwww), but now it tells me, The server encountered an internal error or misconfiguration and was unable to complete your request.
Error Code: 500.

My website is not working at the moment

Check the error logs of the website

What command do I have to put to see the error log of my website?

And where are the sites themselves, what is the PHP version ? And what happens if you change it? I encountered this on 1.8.12, if not changed, the sites were so complicated

This bug appears in the services

Update to the latest version HestiaCp 1.9.2 and it will solve your problem. @ZirexBGR

& apt update
& apt upgrade

It tells me there is nothing to update. I am on 1.9.1 and I am using Ubuntu 24.04.1 LTS

/var/log
for example via FileZilla

We just have released 1.9.2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.