This is an odd issue that I cannot reproduce. Have you tried manually restarting Webmin by running /etc/webmin/restart or /etc/webmin/restart-by-force-kill?
Ran command requested, rebooted and reinserted same var_dump command.
Same result as above.
There is only one cgimode listed in cgimodes array: ‘fcgiwrap’.
It is not possible to have radio buttons when there is only one option. Shouldn’t there be a ‘CGI Scripts disabled’ radio choice, that would arise from a more correct cgimodes array value like [‘fcgiwrap’, ‘cgidisabled’]?
Screenshot for help for ‘CGI script execution mode’:
Since running Nginx, suEXEC wrapper is not relevant
Yes, absolutely and this is exactly what you should see as you have fcgiwrap option in the list of available modes! To be clear, is this Virtualmin Pro package you have installed on this Debian 12 system?
To be clear, I have dozens of test machines, including Debian 12 with Virtualmin GPL and Nginx, and it’s opened right now … and just I don’t see such issue!
I don’t even understand how exactly you could face that issue in the first place (as you showed in the second screenshot)? Unless you mis-edited some Virtualmin files and forgotten about it … as the results you shared are simply impossible – first, because if there are modes available it will simply print those radios (should happen in your case), second if the list is empty, it will just print nothing.
No. I only report such issues after verification with a fresh install on a newly created x86 arch server.
I will try another fresh install from scratch and will choose only the defaults from the Install Wizard, we are invited to complete. I won’t even add in a few favourite extra packages and won’t even run apt update before installing virtualmin.
I just did another fresh install, Debian 12 with Nginx on a rebuilt CPX11 VPS server on Hetzner. Two x86(AMD), that is amd64, VCPUS. 2GB RAM.
No extra packages. No ‘apt update’. Cancelled out of post install wizard to ensure only defaults used. Added a single top-level server using only defaults.
Same problem as reported by me earlier and same as reported just now with Ubuntu by @Stegan.