httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Frost <>
Subject Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution
Date Fri, 11 Jan 2013 13:57:04 GMT

Thank you all for your replies, very helpful and much appreciated.

I understand your thoughts on the IfDefine Proxy, as you can guess this is something which
Epages put in itself, not anything that I put in or use.

When I remove those tags, the DUMP_VHOSTS output is as expected:

VirtualHost configuration:
>          localhost (/etc/httpd/conf.d/ssl.conf:81)
>wildcard NameVirtualHosts and _default_ servers:
>*:80                   is a NameVirtualHost
>         default server (/etc/httpd/conf.d/zzz-epages-httpd.conf:243)
>         port 80 namevhost (/etc/httpd/conf.d/zzz-epages-httpd.conf:243)
>         port 80 namevhost (/etc/httpd/conf.d/zzz-epages-httpd.conf:260)
>Syntax OK

>At this point, it is starting to work more as expected. goes to my second
website, but goes to the default Apache landing page, not to epages. If
I go to the full url (don't normally have to) which would be,
I get the following error:

Service Temporarily Unavailable
>The server is temporarily unable to service your request due to maintenance 
downtime or capacity problems. Please try again later.
The DocumentRoot for epages (the url1 VirtualHost) isn't actually specified in the VirtualHost,
it is specified earlier in the conf file, not in the VirtualHost tags. Putting the DocumentRoot
in the VirtualHost tags for url1 doesnt have any effect.

Please bear with me, and I will post the full config files, hopefully (with much appreciation!)
someone would be able to decipher the epages added in stuff to figure out how it is working.

Thanks again

 From: Igor Cicimov <>
To: users <> 
Sent: Thursday, 10 January 2013, 21:47
Subject: Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

On 11/01/2013 8:46 AM, wrote:
> On 11/01/2013 4:54 AM, "Adam Dosch" <> wrote:
> >
> > On Thu, 10 Jan 2013 17:15:48 +0000, Tom Evans wrote:
> >>
> >> On Thu, Jan 10, 2013 at 12:03 PM, Tom Frost <> wrote:
> >>>
> >>> Hi Adam
> >>>
> >>> Thanks for your reply.
> >>>
> >>> Yes, I did c/p and then replace the domains with the placeholders.
> >>>
> >>> I too noticed that there wasnt any entry for, and I have
> >>> been down the same process you advised of starting with one working and
> >>> gradually adding.
> >>>
> >>> So I start off with httpd.conf and the relevant lines are:
> >>>
> >>> NameVirtualHost *:80
> >>>
> >>> Include conf.d/*.conf
> >>>
> >>> <IfDefine PROXY>
> >>
> >>
> >> Is this so that this vhost is only loaded in the case that the proxy
> >> module is included in Apache?
> >>
> >> If so, I would completely drop it. If the proxy_module is not
> >> available, your website would not work anyway, and better to be told
> >> that when starting apache, than apache to silently drop your vhost and
> >> start up anyway.
> >>
> >> If you did want to keep it (and I correctly guessed why it is there),
> >> you should replace it with this:
> >>
> >> <IfModule proxy_module>
> >>
> >> I would just drop it though.
> >>
> >> With this gone, httpd should see the vhost as the
> >> first and default vhost, and all should work. Please test.
> >
> >
> > Tom F, thanks for posting it all.  I was too lazy to go look back through the list
to find the original postings of your config.
> >
> > I agree with Tom E., dump that <IfDefine PROXY>.  The chances you aren't
going to not load the proxy module some given time I'd say are slim; you're setting it up
for a reason, so it's needed.  Instead of making your configuration 'that' dynamic, if you
decide not to use that vhost for url1 or don't use mod_proxy* for what you're doing, just
remove it and quick change the vhost config.  Keep it simple.
> >
> That has nothing to do with mod_proxy it is variable you set on startup. Read my previous
post. I already suggested to remove it which he did with no result he said. 
> The bottom line is we can discuss this for two years but without knowing the complete
config we are not going to get anywhere. Obviously something specific that epages sets creates
the problem. I suggest op posts the whole config obfuscating the sensitive info if he needs
Plus providing what and how exactly the apache gets started.
> > -A
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
View raw message