Enabling the website option on a domain that had the website disabled prior results in no httpd.conf change

Sorry for the long title.

Today I was trying to add the website option to one of my domains and it struck me that on existing domains that do not have the website enabled yet, this results in weird behaviour.

When I enable the website option the processing results are:

In domain xxx.yyy

Updating Webmin user ..
.. done

<

p> Updating Webmin user ..
.. done

<

p> Saving server details ..
.. done

<

p> Re-loading Webmin ..
.. done

<

p>

Interestingly enough there is no new domain added to apache's httpd.conf and/or the virtual directory where the configuration files are stored (well it's a real directory :)).

When I disable the setting I get:

Deleting virtual website ..
.. no Apache virtual host found!

<

p> Updating Webmin user ..
.. done

<

p> Updating Webmin user ..
.. done

<

p> Saving server details ..
.. done

<

p> Re-loading Webmin ..
.. done

<

p>

Which seems logical because there is no modification seen.

I didn't find something like this 123 on the support forum and/or on the issue list. So I am submitting one . Apologies if this is a duplicate :)

Status: 
Closed (fixed)

Comments

That sounds like a bug .... but on which page did you enable the website for the domain?

Dear Jamie,

Thank you for willing to look into this. I was "editing" the server. I am using the Virtualmin theme, but also the regular theme has the same problem. If you select the domain from within the Virtualmin theme, you can edit the options currently selected for the domain. If you select the website option there, you will get the results that I was facing.

Please let me know in case you need additional information, if you need to access the machine, please let me know in private.

Thanks! Remko

The theme shouldn't make a difference here ...

However, I'd be interested to login to your system to see what went wrong. If that is possible, you can email me at jcameron@virtualmin.com

Also, let me know the domain that you are having this problem with, and if I can try disabling and re-enabling it's website.

I just wanted to add that we are also experiencing this exact issue with the latest version. Attempting to enable the Apache website on a site that does not have it enabled will not create the required Virtual Host files/entries for Apache. The only difference is we're on Ubuntu 10.04.

Ok, I am looking into this now ..

Ok, this is actually a Virtualmin bug :-(

The work-around is to edit the file virtual-server/virtual-server-lib-funcs.pl under the Webmin root directory (typically /usr/share/webmin or /usr/libexec/webmin) and change line 15062 from :

        elsif ($f eq $p) {

to :

        elsif ($f eq $p && $p ne "web") {

Then run /etc/webmin/restart

RemkoLodder - I have already applied this fix on your system.

Dear Jamie,

Yes this seems to work fine! The change for FreeBSD users is propably a bit different (path is /usr/local/lib/webmin/virtual-server) but nevertheless it seems to work fine.

Thanks a lot!

Cheers Remko

Automatically closed -- issue fixed for 2 weeks with no activity.