From: Joaquim H. <jo...@we...> - 2013-01-15 10:26:09
|
How can I control where Virtualmin retrieves the address to use for an Apache website? In the Module Config, I have entered "Default virtual server IP address" as 1.2.3.4, but I still see that VMin creates sites with <VirtualHost *:80></VirtualHost>. I want the IP address to be used in place of '*' as this server has multiple IP addresses. This used to work previously, but at some point during a VMin upgrade, it stopped working. -joho |
From: Jamie C. <jca...@we...> - 2013-01-15 21:13:28
|
On 15/Jan/2013 02:10 Joaquim Homrighausen <jo...@we...> wrote .. > > How can I control where Virtualmin retrieves the address to use for an > Apache website? > > In the Module Config, I have entered "Default virtual server IP address" > as 1.2.3.4, but I still see that VMin creates sites with <VirtualHost > *:80></VirtualHost>. I want the IP address to be used in place of '*' as > this server has multiple IP addresses. > > This used to work previously, but at some point during a VMin upgrade, > it stopped working. Virtualmin will check if in your Apache config you have a NameVirtualHost line with *, or an IP address. If all your NameVirtualHost lines only have IPs, it will put an IP in the <virtualhost> block. - Jamie |
From: Andrey R. <anr...@fr...> - 2013-01-17 00:09:26
|
Greetings, Webmin users list! >> How can I control where Virtualmin retrieves the address to use for an >> Apache website? >> >> In the Module Config, I have entered "Default virtual server IP address" >> as 1.2.3.4, but I still see that VMin creates sites with <VirtualHost >> *:80></VirtualHost>. I want the IP address to be used in place of '*' as >> this server has multiple IP addresses. >> >> This used to work previously, but at some point during a VMin upgrade, >> it stopped working. > Virtualmin will check if in your Apache config you have a NameVirtualHost > line with *, or an IP address. If all your NameVirtualHost lines only have IPs, > it will put an IP in the <virtualhost> block. The NameVirtualHost directive is obsolete, you should not set it, or rely on it's value, for any purpose. -- WBR, Andrey Repin (anr...@fr...) 17.01.2013, <02:56> Sorry for my terrible english... |
From: Cecil Y. Jr. <cj...@yo...> - 2013-01-17 01:18:35
|
On 01/16/2013 02:56 PM, Andrey Repin wrote: > Greetings, Webmin users list! > >>> How can I control where Virtualmin retrieves the address to use for an >>> Apache website? >>> >>> In the Module Config, I have entered "Default virtual server IP address" >>> as 1.2.3.4, but I still see that VMin creates sites with <VirtualHost >>> *:80></VirtualHost>. I want the IP address to be used in place of '*' as >>> this server has multiple IP addresses. >>> >>> This used to work previously, but at some point during a VMin upgrade, >>> it stopped working. >> Virtualmin will check if in your Apache config you have a NameVirtualHost >> line with *, or an IP address. If all your NameVirtualHost lines only have IPs, >> it will put an IP in the <virtualhost> block. > The NameVirtualHost directive is obsolete, you should not set it, or rely on > it's value, for any purpose. > > > -- > WBR, > Andrey Repin (anr...@fr...) 17.01.2013, <02:56> > > Sorry for my terrible english... > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list Pardon my ignorance, but what's taken it's place? -- |
From: Yehuda K. <ye...@ym...> - 2013-01-17 02:05:55
|
On Wed, Jan 16, 2013 at 7:51 PM, Cecil Yother, Jr. <cj...@yo...> wrote: > The NameVirtualHost directive is obsolete, you should not set it, or rely on > it's value, for any purpose. > > Pardon my ignorance, but what's taken it's place? > First, documentation for NameVirtualHost in Apache 2.4: http://httpd.apache.org/docs/2.4/mod/core.html#namevirtualhost The change log for Apache 2.4 notes: The NameVirtualHost directive no longer has any effect, other than to emit a warning. Any address/port combination appearing in multiple virtual hosts is implicitly treated as a name-based virtual host. ( http://httpd.apache.org/docs/2.4/upgrading.html#misc) - Y |
From: Cecil Y. Jr. <cj...@yo...> - 2013-01-17 02:50:33
|
On 01/16/2013 05:38 PM, Yehuda Katz wrote: > On Wed, Jan 16, 2013 at 7:51 PM, Cecil Yother, Jr. <cj...@yo... > <mailto:cj...@yo...>> wrote: > >> The NameVirtualHost directive is obsolete, you should not set it, or rely on >> it's value, for any purpose. > Pardon my ignorance, but what's taken it's place? > > > First, documentation for NameVirtualHost in Apache 2.4: > http://httpd.apache.org/docs/2.4/mod/core.html#namevirtualhost > > The change log for Apache 2.4 notes: > The NameVirtualHost directive no longer has any effect, other than to > emit a warning. Any address/port combination appearing in multiple > virtual hosts is implicitly treated as a name-based virtual host. > (http://httpd.apache.org/docs/2.4/upgrading.html#misc) > > - Y It appears that it's only obsolete if you're using 2.4. If you are still using 2.2.2 NameVirtualHost is still in use. > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > > > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list |
From: Joaquim H. <jo...@we...> - 2013-01-17 09:45:46
|
> Virtualmin will check if in your Apache config you have a NameVirtualHost > line with *, or an IP address. If all your NameVirtualHost lines only have IPs, > it will put an IP in the <virtualhost> block. Fair enough, but shouldn't I be able to override this behavior somehow? I mean, I may actually *want* to specify a given IP address for a site ... no? -joho |
From: Andrey R. <anr...@fr...> - 2013-01-17 20:21:05
|
Greetings, Webmin users list! >> Virtualmin will check if in your Apache config you have a NameVirtualHost >> line with *, or an IP address. If all your NameVirtualHost lines only have IPs, >> it will put an IP in the <virtualhost> block. > Fair enough, but shouldn't I be able to override this behavior somehow? > I mean, I may actually *want* to specify a given IP address for a site > ... no? In Apache prior to 2.4 you'd have to list all possible VHost addresses in NameVirtualHost in order to have Apache recognize these hosts. Which looks a bit stupid and was the case to remove this directive. -- WBR, Andrey Repin (anr...@fr...) 18.01.2013, <00:00> Sorry for my terrible english... |