VIrtualmin restore,Wordpress not working

SYSTEM INFORMATION
OS type and version DEBIAN 12
Webmin version LATEST
Virtualmin version LATEST
Related packages WORDPRESS

After restoring virtualmin servers only one of 3 servers that had wordpress is working.
How to understand why one is working and other two not.

error output
“GET / HTTP/1.1” 500 4932 “-” “Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0”

The output isn’t useful information. We need to see the relevant entries from the error_log for the domain that’s having problems.

[Sun Oct 29 23:22:16.154015 2023] [autoindex:error] [pid 150138:tid 139935755507392] [client 114.119.148.233:45509] AH01276: Cannot serve directory /home/website/public_html/wp-content/themes/enfold/config-layerslider/LayerSlider/static/layerslider/skins/v5/: No matching DirectoryIndex (index.php,index.php4,index.php5,index.htm,index.html) found, and server-generated directory index forbidden by Options directive, referer: https://www.website.gr/wp-content/themes/enfold/config-layerslider/LayerSlider/static/layerslider/skins/v5?C=S%3BO%3DA

i think that i need to extract better logs but i dont know how

Based on the error logs you provided, I would say move the plugin folder inside wordpress to tempory folder. Then try login to the wordpress website.

just inserted LogLevel debug rewrite:trace8 on apache conf files and i have better logs.

Did you try what I suggested to do ?

I think this is easily explained.
The one that is working is different to the two that are not. most likely in their state of having been updated or (same thing) in their different use of plugins/theme.

There is a pointer in that log message to the theme that is causing the problem and why.

I doubt if this has anything to do with Virtualmin (why were you “restoring Virtualmin” and how, what were the changes made to Virtualmin from the presumably working system?) Is this a new, clean install? on what (we are missing that important System information) were these “restored” from a backup. why?

The http 500 error is also a rough guide where to look. It typically is the end result of a database error. So is the non-working site attempting to update (reconfigure a table in MariaDB?) → probably, as themes store their status in the Db.

i did it and nothing changed

mv wp-content/plugins temp

Some direction?

Thank you.

So after moving the plugins to temp folder. Are you still getting the error 500 code?

Yes the same 500 code

I have to say that if i insert any html page with anything inside (test page)browsing page is possible
without any problem.

Jave you looked at you .htaccess file ? All I’m thinking is this file contains some php directives that are not valid for the execution mode of php you are using. Try changing the php execution mode to something different. At a guess I would think your old system was using apache mod php and you are now using php-fpm

.htaccess file is the same on all 3 wordpress sites

i changed php mode to fcgi etc but again nothing changed…

You still have not given us that important information: We need the history of how you got where you are

Why were you making this change in Virtualmin?

What were you changing from?

You had a fully working system with 3 domains.

You did something to get where you are now → a system with one of three working.

Without that information we can only make educated guesses

I had a old virtualmin installation with debian 9 or 10.
5 years around and was time to do a clean install.
From debian 9 to Debian 12 clean install.

Than you,
So working ok on Debian 9. but not on Debian 12.

The sites were backed up → can you remember which version of Virtualmin was on the Debian 9 box. Also what version of PHP was running there?

I am assuming Apache on both old and new.

Debian 9 to 12 is quite a big move in itself. I’m not sure I would have made such a leap on a production VS. 12 has some issues when moving from 11 that have been discussed on here (but I don’t think they are relevant here).

WordPress has also gone through many changes in 5 years. I do hope all those updates were applied prior to the backup → 5 years is along time in IT

virtualmin-core 6.0.1
php 7.3