On 9/21/21 18:52, Frank Gingras wrote:
> I would not rely on the debian scripts. Looking at apachectl -S will tell
> you what you need to know.
>
> On Tue, 21 Sept 2021 at 18:51, Frank Gingras wrote:
>
>> Why do you have two vhosts with the same ServerName value set? That will
Off topic
The host I'm using was originally named accordingly with the task
assigned back then, now one of the vhosts has the same name.
But, after noticed the issue just renamed the conf, and now everything
is working as expected.
Thank you all for your time and patience.-
El 2021-09-21 19:51,
I would not rely on the debian scripts. Looking at apachectl -S will tell
you what you need to know.
On Tue, 21 Sept 2021 at 18:51, Frank Gingras wrote:
> Why do you have two vhosts with the same ServerName value set? That will
> break name-based vhosts. Set a unique ServerName value for every
Why do you have two vhosts with the same ServerName value set? That will
break name-based vhosts. Set a unique ServerName value for every vhost on
that port.
On Tue, 21 Sept 2021 at 18:25, Daniel Armando Rodriguez
wrote:
> Here it is the curl result from the same host
>
> # curl -v -H
On 2021-09-21 6:25 p.m., Daniel Armando Rodriguez wrote:
Here it is the curl result from the same host
[snip]
From apachectl -S I see the problem is related to what vhost is set as
default
VirtualHost configuration:
*:80 is a NameVirtualHost
default server
Here it is the curl result from the same host
# curl -v -H Host:4.DOMAIN.edu.ar http://INTERNAL-IP/
* Expire in 0 ms for 6 (transfer 0x5573684c6c10)
* Trying INTERNAL-IP...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x5573684c6c10)
* Connected to INTERNAL-IP (INTERNAL-IP) port 80
Show the httpd -S output and results from your tests with curl, then.
It might help to log the host: header in your access log too.
On Tue, 21 Sept 2021 at 17:41, Daniel Armando Rodriguez
wrote:
> Changed all vhosts definition the way you suggested, but the issue still
> happens.
>
>
> El
Changed all vhosts definition the way you suggested, but the issue still
happens.
El 2021-09-21 16:32, Frank Gingras escribió:
The first mistake is to use the hostnames when defining vhosts. Define
them all as *:PORT, then test with curl, and run apachectl -S or httpd
-S to spot any overlap.
El 2021-09-21 16:47, Darryl Philip Baker escribió:
I have ~200 virtualhosts on my Apache HTTPD server and all use the
declaration “” with not port specification. Just a
“Listen 80” directive. Do you specify the port on the VirtualHost
directive because you don’t want to accept traffic on all the
e.
>
> Suite 6-600 – Box #39
>
> Evanston, IL 60201-3715
>
> *darryl.ba...@northwestern.edu *
>
> (847) 467-6674 <+18474676674>
>
>
>
>
>
> *From: *Frank Gingras
> *Reply-To: *"users@httpd.apache.org"
> *Date: *Tuesday, September 21, 2
Reply-To: "users@httpd.apache.org"
Date: Tuesday, September 21, 2021 at 2:32 PM
Cc: "users@httpd.apache.org"
Subject: Re: [users@httpd] Four subdomain, fourth redirects to first
The first mistake is to use the hostnames when defining vhosts. Define them all
as *:PORT, then test with
The first mistake is to use the hostnames when defining vhosts. Define them
all as *:PORT, then test with curl, and run apachectl -S or httpd -S to
spot any overlap.
On Tue, 21 Sept 2021 at 14:48, Daniel Armando Rodriguez
wrote:
> Hi,
>
> I have four subdomains on the same host which work as
Hi,
I have four subdomains on the same host which work as expected whis this
base config
ServerName 4.DOMAIN.edu.ar
ServerAlias 4.DOMAIN.edu.ar
ServerAdmin webmas...@domain.edu.ar
DocumentRoot /var/www/4
Options FollowSymLinks
AllowOverride All
Require all granted
13 matches
Mail list logo
