Virtualmin Configuration Changes Not Taking Effect

SYSTEM INFORMATION
OS type and version Ubuntu 24.04 LTS
Webmin version 2.302
Virtualmin version 7.80
Webserver version Apache 2.4.58
Related packages PHP 8.3, MariaDB 10.11, Perl 5.38, OpenSSL 3.0

I’m experiencing an intermittent issue on my Virtualmin server where configuration changes made for a virtual server do not always take effect immediately. After modifying settings through Virtualmin and saving the changes, the interface reports that the operation completed successfully, but the website sometimes continues to behave according to the previous configuration. The issue is inconsistent because the same type of change may work normally on one occasion but appear to be ignored on another.

I have tried saving the virtual server configuration again and restarting or reloading the web server, but this does not always resolve the problem. In some cases, the new configuration eventually becomes active after some time, while in other cases I have to make another change or reload the service before the expected behavior appears. There are no obvious errors shown in the Virtualmin interface, so I am unsure whether the problem is related to configuration generation, service reloads, virtual host configuration, or another component on the server.

I would like to troubleshoot this properly rather than repeatedly restarting services. Is there a recommended way to verify that Virtualmin has generated the correct configuration files and that the web server is actually loading those files? I am also wondering whether there are specific Webmin, Virtualmin, Apache/Nginx, or system logs that should be checked when a configuration change appears to save successfully but does not become active. Any commands that can help compare the generated configuration with the currently loaded configuration would also be useful.

Has anyone experienced Virtualmin configuration changes being saved successfully but not immediately reflected by the web server? What would be the best way to identify where the configuration update is getting delayed or not being applied?

What specifically isn’t taking effect? Is it being changed through the virtual server’s configuration options or the more general “virtualmin configuration” or “server templates” section? I’m not sure which exactly, but some options don’t take effect until a new virtual server is created, or a validation check is run; it depends on the option/location etc. It seems like you have questions about multiple scenarios, and it would be helpful for someone else to help with specifics. Hope this helps to start to narrow some stuff down.

With Ubuntu, you can usually run systemctl status <service> to get an idea if that service is running or has some errors preventing a reload/restart. journalctl -u <service> can be helpful to get logs, some services might still leave files in the /var/log/ directory.

could be browser cache or proxy cache if you using cloudflare.
Virtualmin just makes changes to the web server, it would not normally be the problem.
Do you see the config changes in the configuration files of the server.

The symptoms sound very much like caused by caching.
I second stefan’s thoughts.

I have had very annoying caching when dealing with Cloudflare, even with proper caching configuration (which should respect the page’s headers). I eventually added a Cloudflare rule to disable caching when there is a Wordpress authentication cookie, and this worked well.

In addition to this seeming like a made up problem (I don’t know how it would do what is being described, Virtualmin edits config files directly, there is no caching layer or intermediate database) I’m finding the ancient versions of packages suspicious. Seems like maybe this is engagement bait written by an LLM.

If I don’t see some human-sounding follow up, I’m inclined to delete and ban.

OP: Update your software to current versions and follow up.

I’m not suggesting that Virtualmin has a separate caching layer; the issue I’m trying to understand is that Virtualmin reports the configuration change as completed, but the behavior I expect from the web server does not always change immediately afterward.

I’ll update the software to current versions first as you suggested and then reproduce the issue with the updated environment.

Can you provide an example of what configuration isn’t changing and what in particular is being done beforehand?

Apologies for accusing you of being a machine (we get a lot of engagement bait written by LLMs, most of it gets flagged immediately by our antispam system).

As Ilia notes, I think we need specific details. What specific thing are you changing that doesn’t take effect immediately after saving?