I think I have managed to solve the problem :-) actully, seems I created it as
well :S.
First: I thought that by setting a two virtualhosts virtualhost named
000-default, set to listen *:80 and *:443 respectively, I would have made those
virtualhosts the default for all the interfaces. However,
On Sat, Oct 3, 2015 at 4:25 PM, Felix Rubio Dalmau
wrote:
>
> After this change, if I ping site3.example.com, the address is properly
> resolved to the vpn (10.8.0.1). Then, from Firefox, I access
> http://site3.example.com and the URL is magically converted into
> https://site3.example.com, an
Hi Yann,
At first, I have executed apachetl -S and this is what I have obtained:
===
10.8.0.1:443 site0.example.com
10.8.0.1:80is a NameVirtualHost
default server site0.example.com
port 80 namevhost site0.example.com
port 80 namevho
Hi,
can you provide the output of "apachectl -S"?
You may hide real names with site1, site2, ... but please keep one
name per orinal name.
Regards,
Yann.
On Tue, Sep 29, 2015 at 8:07 PM, Felix Rubio Dalmau
wrote:
> Hi Marat, httpd-users :)
>
>
>
> I have updated the configuration of my apache.
I suspect something beyond virtualhost selection. Can you please:
1. Share more about the way site directories on server are specified.
DocumentRoot, Alias'es, Redirect's etc.
2. Share access logs to make sure Apache is accessing same virtualhosts
we think it is accessing. :)
Also, is it po
Hi Marat, httpd-users :)
I have updated the configuration of my apache. Following these lines
there is the updated version. The behavior now is:
a) If I type in the url box the non-ssl address of site1 IN FIREFOX, It
gets transformed into the ssl address of site0, and its conten
This is very strange. Even when Apache cannot determine request host
name, it loads the first defined virtual host, not the last one. I
wonder, in your case, what will it load if you disable last two virtual
host records?
(BTW, it's usually either Listen 80, or Listen specific-ip:80, but I
do
Hi,
No, the reason is that site2 holds a cardav server, that is accessed by
other of the sites on the same host. The idea behind this is that I can
save all the time spent in encryption (the SSL layer) if I know that both
sites are local.
I am testing this configuration from a client on the VP
Hello,
127.0.0.1 is only configured for site2 -- is it a bug or a feature? Are you
testing it from the same host, or via proxy on the same host?
--
With Best Regards,
Marat Khalili
On September 28, 2015 10:06:04 PM GMT+03:00, Felix Rubio
wrote:
>Hi everybody :-)
>
>I have an Apache server (2
Hi everybody :-)
I have an Apache server (2.4) running on a Debian testing. Because I need to
access some sites from Internet (iface 192.168.1.2)(with and without SSL), some
others through a VPN (iface 10.8.0.1) and some others are purely local to the
server (iface 127.0.0.2), I have created th
On Fri, Jan 11, 2013 at 1:57 PM, Tom Frost wrote:
> Hi
>
> 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
___
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, icici...@gmail.com wrote:
>
>
> On 11/01/2013 4:54 AM, "Adam Dosch" wrote:
On 11/01/2013 8:46 AM, icici...@gmail.com wrote:
>
>
> On 11/01/2013 4:54 AM, "Adam Dosch" wrote:
> >
> > On Thu, 10 Jan 2013 17:15:48 +, Tom Evans wrote:
> >>
> >> On Thu, Jan 10, 2013 at 12:03 PM, Tom Frost wrote:
> >>>
> >>> Hi Adam
> >>>
> >>> Thanks for your reply.
> >>>
> >>> Yes, I did
On 11/01/2013 4:54 AM, "Adam Dosch" wrote:
>
> On Thu, 10 Jan 2013 17:15:48 +, 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 noti
On Thu, 10 Jan 2013 17:15:48 +, 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 url1.mydomain.com, and
I have
been down the
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 url1.mydomain.com, and I have
> been down the same process you advised of starting with on
>
>
> ServerName url1.mydomain.com
> ServerAlias surl1.mydomain.com
> VirtualHost configuration:
> 127.0.0.1:443 localhost (/etc/httpd/conf.d/ssl.conf:81)
> Syntax OK
>
> So, again, as you mentioned, Apache doesnt know what to do with
> url1.mydomain.com. Is this because the VirtualHost
______________
From: Adam Dosch
To: Tom Frost ; users@httpd.apache.org
Sent: Wednesday, 9 January 2013, 17:36
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
Tom,
Sorry for the belated reply.
> The output requested is:
>
>
-t -D DUMP_VHOSTS' and from a web browser. From there once
you get it nailed down, then do any merging for maintenance sake on your
.conf files.
Hope that helps.
-A
-
FROM: Adam Dosch
TO: Tom Frost ; users@httpd.apache.org
SENT: Thursday, 3 January 2013, 19:2
Ah yes, sorry, there is the standard:
Include conf.d/*.conf
I will try commenting the zzz-epages-*.conf
Thanks
Tom
From: Tom Evans
To: users@httpd.apache.org; Tom Frost
Sent: Wednesday, 9 January 2013, 9:41
Subject: Re: [users@httpd] VirtualHost
On Tue, Jan 8, 2013 at 1:33 PM, Tom Frost wrote:
> Hi Tom
>
> Dont think so, the different epages configs are included like this:
>
> Include /etc/httpd/conf.d/zzz-epages-*.conf
>
> And there is only one zzz-epages-httpd.conf
>
> Thanks
>
> Tom
>
And nothing else is doing something like "Include
2013, 15:42
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
On Mon, Jan 7, 2013 at 3:02 PM, Tom Frost wrote:
> Hi
>
> Thanks for your reply Adam.
>
> The output requested is:
>
> VirtualHost configuration:
> 127.0.0.1:443
On Mon, Jan 7, 2013 at 3:02 PM, Tom Frost wrote:
> Hi
>
> Thanks for your reply Adam.
>
> The output requested is:
>
> VirtualHost configuration:
> 127.0.0.1:443 localhost (/etc/httpd/conf.d/ssl.conf:81)
> wildcard NameVirtualHosts and _default_ servers:
> *:80 is a Name
g the _default_
anymore, just both *:80.
Thanks again,
Tom
From: Adam Dosch
To: Tom Frost ; users@httpd.apache.org
Sent: Thursday, 3 January 2013, 19:28
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
Tom,
I
they are you need to start
apache with -DPROXY switch or that vhost will not be active at all due to
IfDefine condition
_______
> From: Tom Frost
> To: "users@httpd.apache.org"
> Sent: Thursday, 3 January 2013, 13:58
> Subject: Re: [users@httpd
t vhost will not be active at all
due to IfDefine condition
___
> From: Tom Frost
> To: "users@httpd.apache.org"
> Sent: Thursday, 3 January 2013, 13:58
> Subject: Re: [users@httpd] VirtualHost configuration not working as
expected with ePages solutio
Tom,
I'd be curious what the output of your 'apachectl -t -D DUMP_VHOSTS'
looks like?
I've come across this problem as well in a related degree, and
interrogating the output of the 'DUMP_VHOSTS' above will at least tell
you the top-to-bottom order your vhost requests will travel down in your
t I'm honestly not sure what is what.
Thanks again for your help, any more suggestions would be appreciated.
- Original Message -
From: Eric Covener
To: users@httpd.apache.org; Tom Frost
Cc:
Sent: Thursday, 3 January 2013, 15:14
Subject: Re: [users@httpd] VirtualHost configuration not
On Thu, Jan 3, 2013 at 8:58 AM, Tom Frost wrote:
> Hi
>
> I have changed both VirtualHost definitions to *:80 and NameVirtualHost has
> the same, however both whichever hostname I use I still get the same site.
> Does it matter that the VirtualHost definitions are in separate config
What hostname
On Thu, Jan 3, 2013 at 9:01 AM, Tom Frost wrote:
> Just to clarify, this is how the conf files look now:
>
> httpd.conf:
>
> NameVirtualHost *:80
>
>
>
> DocumentRoot /var/www/html/path/
> ServerName url2.mydomain.com
> ServerAlias url2.mydomain.com
>
>
> epages.conf:
>
>
>
> ServerName url1.
: Thursday, 3 January 2013, 13:58
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
Hi
I have changed both VirtualHost definitions to *:80 and NameVirtualHost has the
same, however both whichever hostname I use I still get the same site. Does it
m
Covener
To: users@httpd.apache.org; Tom Frost
Sent: Thursday, 3 January 2013, 12:02
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
>
>
These have to be the identicalvalues for name-based vhosts to treat
them as part of a set.
If you
>
>
These have to be the identicalvalues for name-based vhosts to treat
them as part of a set.
If you don't care what IP address is used, use *:80 for both. If you
do care, use t my.ip.add.res:80 for both. NameVirtualHost should have
again an identical argument.
--
Eric Covener
cove...@gmail.
: Thursday, 3 January 2013, 11:36
Subject: Re: [users@httpd] VirtualHost configuration not working as expected
with ePages solution
What Apache version are you running?
Have you added something like below in httpd.conf
NameVirtualHost your_ip_address:80
then
DocumentRoot /var/www/html/path
What Apache version are you running?
Have you added something like below in httpd.conf
NameVirtualHost your_ip_address:80
then
DocumentRoot /var/www/html/path
ServerName another.url.com
ServerAlias another.url.com
Replace your_ip_address with the IP of the machine Apache is running on
On T
Hi
I have a Centos server running ePages (which runs on Apache). Now I want to use
the same server to host a couple of other sites as well, but I can't seem to
get my configs working correctly. I'm not sure if anyone is familiar with
epages (I've looked on their forums to no avail), but this is
36 matches
Mail list logo
