I have several domains hosted in virtualmin, that for example use mail and some other hosted service as nextcloud to share agendas, contacts, etc.. and have the web hosted on an external server, then the records www.mydomain.com and mydomain.com point to the ip of the external web server, this works fine until I want to enable roundcube or nextcloud and virtualmin only allows me to do it in www. mydomain.com/nextcloud… etc… but always www.mydomain.com as this record points outside, logically does not work, the quick solution I used is to create an alias that hangs from the main domain called app.mydomain.com and here I put roundcube and nextcloud for example, but it counts as one more domain in virtualmin licenses and I do not consider that it is the most correct.
Is there a better way?
I think the ideal would be that the virtualmin installer would ask me all the path and let me put in the initial installation for example nextcloud.mydomain.com that would be the most correct, is it possible ???
Yes, of course, you can edit everything that comes after domain.com or www.domain.com, but if as I said you have the web on another server, these two records point to an external IP so it is useless to put domain. com/nextcloud because it will go to look for the external server, so I ask that I would like to be able to choose the full path such as nextcloud.domain.com, so this record could go to the ip of the virtualmin server
It is changing the concept on which virtualmin has been built that yes or yes domain.com has to point to the ip of the virtualmin server.
Yes, I’ll try to explain it again from the beginning…
By concept (I think wrong, so I think it would be better to change it) Virtualmin installs the Web apps always under the main domain → www.mydomain.com/nextcloud .. /roundcube,etc … there are environments / domains where the web designer requires you to have it on your external hosting, so in these cases www. mydomain.com and mydomain.com points to an external ip to virtualmin, in these cases I can not install web apps like nextcloud, roundcube, etc.. without creating a subserver as apps.domain.com, I do not really like this option among other things because it counts as two licenses / domains.
If the webapss installer would just let me install on nextcloud.mydomain.com for example, I would avoid having to create a new sub-server, etc… I think it is too much work for everyone.
ignoring the licencing issue for a moment.
does it work that way? (I do have a number of VMs on GPL and I think that was my approach to a similar website running on an external domain.)
I have to admit that I have never quite understood why subdomain.example.tld is treated the way it is
Yes, of course it works that way, but having to generate a new domain or subdomain for that is not logical.
Thanks, I see that at least I’m not the only one who thinks so, maybe it’s time to reconsider the wep apps generation script, I don’t think it’s so difficult, it’s just let put one more field, not take for granted that it’s www.mydomain.com + whatever you want to put, but directly let put cname+route
I know outside of Pro it was relatively simple (I must search my notes) - I have to say it involved no CLI (but I guess it could be done that way) It was on a LEMP installation (so I expect some .cfg steps. I would probably approach it differently these days
You’re only using this for email, as the website is on another server.
As far as I know virtualmin hasn’t actually got an email only option, so will install a website as well.
So if you use the script installer to install Nextcloud or whatever on this server it will install on (www.)mydomain.com(/whatever)
If there would be a setting in the script installer to change this to e.g. nextcloud.mydomain.com then who’s going to tell apache (or nginx) where to find the files?
I’ll give you a clue, you are, by installing a sub server or alias server.
Then run the script installer from there.
That’s how it’s supposed to work.
If you want the script installer to install on nextcloud.mydomain.com even though you’re working with the server (www.)mydomain.com and are then planning to make manual changes to the apache conf files, you might as well ditch virtualmin all together and do everything by hand.
Just my 2p
Edit: just noticed you’re worried about the pro license count. An alias server does not take up a separate license
That is not the problem, I have been paying Virtualmin for more than 20 years, a license for 100 domains when I only have 50 in use, so that is NOT the problem
I am simply saying that the script should NOT assume that the path is www.mydomain. com, but should also be able to change it, it is a very simple change to make
As I said it is increasingly common for a designer to tell a company that the new website goes on your hosting, and suddenly that company that I take the hosting, I have to change the path of webmail, nextcloud, etc … because Virtualmin does not allow me to choose the part of www.mydomain.com and I have to create a subdomain having to change everything and everywhere.
