i am having getting this same error
and i realize what it is saying..
but i cannot get it to let me create an SSL.. the bottom option only allows me to enter an ip and doesnt allow me to specify virtual like in the screen shot for the domain creation page in docs here..
I am using x.x.9.1 on eth0 (only primary eth interface) I have added eth0:2 -> eth0:63 with addresses of x.x.9.2 -> x.x.9.63
net int for virt is eth0 base num for vert is x.x.9.2 def virt serv ip is x.x.9.1
under the default template i added x.x.9.2 -> x.x.9.63 to assignable address range..
does any know why I cant choose virtual in domain creation ??
Hi Benjamin,
Virtualmin will add the alias for you--you don't need to pre-create them. I don't know if that is the source of your trouble, but it might be.
If not, send the actual error message you're getting and I'll see if I can reproduce it.
--
Check out the forum guidelines!
well thats how i started out..
ie without any interfaces... it didnt show the option so i assumed i needed to make them
i will go ahead and remove all my ifcfg-eth0:* files now..
but....
it makes no difference.. i dont get the option..
there really is no "error" message.. i get the error when making an ssl that i need to use a virtual.. turn off SSL and everything works fine.. I just dont have the option to use a virtual when creating a domain..
i dont have the radio buttons. i have a text field that defaults to my primary ip...
this should give you a good idea of my problem
http://www.direclynx.net/~cthulhu/images/problem.jpg
http://www.direclynx.net/~cthulhu/images/shouldbe.jpg
the docs imply that it will auto create a new int for you..
and that it doesnt require the person adding the domain to know anything at all.. ie the reseller cant see which ips are used so far so he cant be expected to know what to manually enter..
also.. some automation is implied with the auto assign ip range entered in templates
any news ???
any news ???
ive got this one small issues
once this is solved I will be buying two more copies...
Benjamin.
I guess this is jamie's issue, so i am creating a new bug for you. So he notices this and can comment on it. You can check the buf tracker!
Faisal.
Sorry Benjamin, this issue crept off of my radar for a moment.
This is probably a bug in the installer, rather than in Virtualmin, but it is definitely a problem that needs to be fixed. I suspect it is a configuration option that is set incorrectly during setup. I'm looking into it now...should have an answer in a few minutes.
--
Check out the forum guidelines!
Hi Benjamin,
If you have entered an IP range for automatic allocation on the Server Templates page, when you create or edit a server Virtualmin doesn't prompt you to enter an IP manually. Instead, it will pick one for you that is free in the specified range.
Make sure that you don't being up any of those IPs manually though .. Virtualmin will do this for you automatically.
--
Check out the forum guidelines!
please read the whole thread..
this is not the case
nope... this is not the case..
it still gripes eveytime I try to add an ssl website
I do have a range set in the template
any news..
please read all the info and look at the screenshots above..
I DO NOT HAVE AN OPTION FOR VIRTUAL IP WHEN ADDING A WEBSITE
ONLY THE TEXT BOX FOR MANUAL ENTRY
simply put.. from a fresh install..
it is not recognizing that I have or that I can have more than one IP...
Hey Benjamin,
OK, let's get this thing straightened out, one piece at a time.
You're not getting the "Shared, on IP" bit on your page because you have configured your server to <i>always</i> create an SSL domain. These cannot be shared, and so there would be no reason to offer you the option. This is expected behavior, though maybe not obvious. To get the "Shared, on IP" option back, edit your module configuration and change "SSL website setup enabled?" from "Yes" to "Yes, but not by default".
Obviously, this shouldn't effect the ability to save a domain with SSL enabled, so we've got to keep digging.
I'm able to reproduce the problem and it is a subtle one, but it is actually a bug in Virtualmin that will be fixed.
Here's the explanation of what's happening:
You already have one or more domains configured on the shared IP.
You are now creating an SSL domain, which needs a new IP. So Virtualmin goes to its configuration to see what the next virtual IP should be. The default tells it to start with the primary address of the default interface...but we've already used it for shared hosts, so we can't use it for SSL!
Virtualmin ought to recognize that it needs a new IP, and bump the number up to the next non-existent one...but it doesn't, and there doesn't even appear to be a way to workaround it.
I've filed a high priority bug on this issue. Jamie will get us a workaround or a fix shortly.
Sorry this took so long to get some kind of answer about what's happening, I was so busy worrying about the missing "Shared IP" but that I didn't really get around to paying attention to the real problem.
--
Check out the forum guidelines!
actually it was not "always use ssl" i had created quite a few sites already.. all of them shared.. Jamie's response fixed it..
not really a bug.. a mistake on my part coupled with a small lapse in documentation..
Hi Benjamin,
One possible cause of the confusion could be that the option 'All Apache virtual servers are name-based?' is set to 'Yes' on the Module Config page. This should really be set to 'No' unless you aren't doing any IP-based hosting, which is not the case on your system.
Try changing that option to 'No' and then creating a new virtual server..
--
Check out the forum guidelines!
you are correct sir..
i played with too many knobs and dials..
thanks for the fix..
im proceeding with my setup..
thanks again