You can also try to replace "IncludeOptional conf.d/*.conf" by
"IncludeOptional /etc/httpd/conf.d/*.conf"
Le 13/12/2020 à 18:26, Daniel Ferradal a écrit :
check "apachectl -S" output to make sure what virtualhosts you are really using.
El dom, 13 dic 2020 a las 15:20, Richard B. Pyne ()
check "apachectl -S" output to make sure what virtualhosts you are really using.
El dom, 13 dic 2020 a las 15:20, Richard B. Pyne () escribió:
>
> Hi Lucien,
>
> Yes. that is the case. It is /etc/httpd/conf.d
>
> The last line of the main config file /etc/httpd/conf/httpd.conf file is
>
>
Hi Lucien,
Yes. that is the case. It is /etc/httpd/conf.d
The last line of the main config file /etc/httpd/conf/httpd.conf file is
IncludeOptional conf.d/*.conf
On 12/13/2020 5:38 AM, Lucien Gentis wrote:
Hello Richard,
I don't know how CentOs configures httpd, but I suppose You have a
Hello Richard,
I don't know how CentOs configures httpd, but I suppose You have a main
config file which includes all config files contained in
/etc/httpd/conf.d ; is it the case ?
Le 13/12/2020 à 13:26, Richard B. Pyne a écrit :
I know this has been asked numerous time, and I have read
On Fri, 28 Sep 2018 15:40:49 +0200, Sander Smeenk stated:
>Quoting Carmel NY (carmel...@outlook.com):
>
>> >Please elaborate on the 'not working out so well' bit.
>
>> >> apachectl -S
>> >> VirtualHost configuration:
>> >> *:80 stem.example.net
>> >>
Sorry, I need to correct my English. Seems my fingers don't find the
right keys all the time ;)
On 9/28/18 7:10 AM, Carmel NY wrote:
> Okay, on a stock FreeBSD installation, maybe on others too, there is an
> index.html file in the document root that displays,
In my experience you can't
On 9/28/18 7:10 AM, Carmel NY wrote:
> Okay, on a stock FreeBSD installation, maybe on others too, there is an
> index.html file in the document root that displays,
In my experience you can't expect a stock instllation to work,
especially since you seem to be pointing at different directories
On 9/28/18 5:21 AM, Sander Smeenk wrote:
> Quoting Carmel NY (carmel...@outlook.com):
>> This is my first attempt to set up a virtual host with apache24 on a
>> FreeBSD 11.2 machine, and it is not working out so well.
>
> Please elaborate on the 'not working out so well' bit.
>
>
>> Assuming a
Quoting Carmel NY (carmel...@outlook.com):
> >Please elaborate on the 'not working out so well' bit.
> >> apachectl -S
> >> VirtualHost configuration:
> >> *:80 stem.example.net
> >> (/usr/local/etc/apache24/extra/httpd-vhosts.conf:24)
> >> *:443 example.net
Oh, I missed that my first time through. Is there anything in the log
files that you specify in the virtual host?
On Fri, Sep 28, 2018, 05:51 Carmel NY wrote:
> On Fri, 28 Sep 2018 05:32:16 -0600, Jonathon Koyle stated:
>
> >On Fri, Sep 28, 2018, 05:10 Carmel NY wrote:
> >
> >> On Fri, 28 Sep
On Fri, 28 Sep 2018 05:32:16 -0600, Jonathon Koyle stated:
>On Fri, Sep 28, 2018, 05:10 Carmel NY wrote:
>
>> On Fri, 28 Sep 2018 11:21:36 +0200, Sander Smeenk stated:
>>
>> >Quoting Carmel NY (carmel...@outlook.com):
>> >> This is my first attempt to set up a virtual host with apache24 on a
>>
I wonder if the :80 in the ServerName directive is causing you grief, since
it isn't passed that way for http?
On Fri, Sep 28, 2018, 05:10 Carmel NY wrote:
> On Fri, 28 Sep 2018 11:21:36 +0200, Sander Smeenk stated:
>
> >Quoting Carmel NY (carmel...@outlook.com):
> >> This is my first attempt
On Fri, 28 Sep 2018 11:21:36 +0200, Sander Smeenk stated:
>Quoting Carmel NY (carmel...@outlook.com):
>> This is my first attempt to set up a virtual host with apache24 on a
>> FreeBSD 11.2 machine, and it is not working out so well.
>
>Please elaborate on the 'not working out so well' bit.
>
>
Quoting Carmel NY (carmel...@outlook.com):
> This is my first attempt to set up a virtual host with apache24 on a
> FreeBSD 11.2 machine, and it is not working out so well.
Please elaborate on the 'not working out so well' bit.
> Assuming a site name of example.net, I tried to configure a
Hi David,
2018-01-29 19:45 GMT-08:00 David Mehler :
> Hello,
>
> Can someone take a look at the below virtual host configuration?
> Whenever I put it in my apache 2.4 the server returns an alert
> unexpected network read error connection aborted message. If I take it
> out
Hello,
Thanks. That sure made my file easier to handle.
One thing can I using redirect go from http to https? Like example.com
redirects to https://www.example.com?
Thanks.
Dave.
On 7/16/17, Daniel wrote:
> Redirect is simpler as you can see, it redirects everything, it
Redirect is simpler as you can see, it redirects everything, it has a
regex version called RedirectMatch. Both are provided by mod_alias.
RewriteRule is for more complex things, yes it can redirect too, but
as you have seen yourself, the most simple thing can bring confusion.
RewriteRute is
Hello,
Thanks. I'll try the rewrite redirect.
With regards the redirect option, the simpler way, does it do the tls
conversion unsecure to secure? What would the advantages/disadvantages
of rewrite and redirect?
Thanks.
Dave.
On 7/16/17, Daniel wrote:
> And while at it
And while at it why not use simple Redirect's since your config fits
perfectly to use them:
ServerName example.com
Redirect / http://www.example.com/
simpler, gets the job done, and you don't need a cannon to smash a fly.
2017-07-16 17:48 GMT+02:00 Luca Toscano
Hi David,
2017-07-15 3:11 GMT+02:00 David Mehler :
> Hello,
>
> I'm running Apache 2.4 on a FreeBSD 10.3 system, with several virtual
> hosts. My goal is to have all of them completely ssl, except for the
> .well-known area needed for letsencrypt.
>
>
> ServerName
It seems that once you use virtual hosting, you really need to define a
default virtual host by making something the first in the config file.
On a server without virtual hosts, I have:
VirtualHost configuration:
ServerRoot: "/etc/httpd"
Main DocumentRoot: "/var/www/html"
Main ErrorLog:
rols who can get stuff from this server file
>>
>> Order allow,deny
>>
>> Allow from all
>>
>>
>>
>>
>>
>> ServerEnvironment apache apache
>>
>>
t 11:40 AM
To: "<users@httpd.apache.org>" <users@httpd.apache.org>
Subject: Re: [users@httpd] Virtual Host - Port 80 to 443
is totally invalid. Use *:80 or *:443 or ip:port but never "*"
alone.
Also if you define *:80 and there you want to redirect to the SSL virtual
is totally invalid. Use *:80 or *:443 or ip:port but never
"*" alone.
Also if you define *:80 and there you want to redirect to the SSL
virtualhost by all means use the http scheme in the redirect directive like:
Redirect permanent / https://subdomain.domain.ac.za/
2016-07-14 11:31 GMT+02:00
On 05/14/16 18:19, Frank Gingras wrote:
On 14/05/16 07:53 PM, phil wrote:
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez <miguel_3_gonza...@yahoo
On 14/05/16 07:53 PM, phil wrote:
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez <miguel_3_gonza...@yahoo.es>
To: Beech <akbe...@gmail.co
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez <miguel_3_gonza...@yahoo.es>
To: Beech <akbe...@gmail.com>, users@httpd.apache.org
I alwa
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez <miguel_3_gonza...@yahoo.es>
To: Beech <akbe...@gmail.com>, users@httpd.apache.org
I always have used either the ip address or
I always have used either the ip address or the wildcard * in the virtualhost
directive.
Have you checked the logs?
Beech wrote:
>I have added a new virtual domain and it's not working. No error
>messages, just won't connect. I have triple checked the paths and
>spelling.
On Sat, Feb 13, 2016 at 6:43 AM, Meta Correio
wrote:
> So, the question is, why does Apache place both requests under the same
> Virtual Host when, on a scenario using Virtual Hosts under the
> NameVirtualHost paradigm it should look at the Host: to decide what Virtual
>
On 07/23/2015 03:48 PM, Mathijs Schmittmann wrote:
K R schreef op 7/23/2015 om 9:44 PM:
Hi,
my customer want to configure virtual host for 5 website in one apache
environment . do i have to get 5 ip addresses from network team.
Can someone please point me on how can i achieve the same
No,
K R schreef op 7/23/2015 om 9:44 PM:
Hi,
my customer want to configure virtual host for 5 website in one apache
environment . do i have to get 5 ip addresses from network team.
Can someone please point me on how can i achieve the same
No, you should create 5 virtualhosts in your
On Mon, Feb 10, 2014 at 10:24 PM, Jim Borland jborl...@calpoly.edu wrote:
My server, which is located in the Amazon cloud, was just moved to a new
location with a new IP address. Nothing else was changed. However, the
Apache Virtual Host, which has worked flawlessly for several years, is
My goodness, that worked! I am blown away! Thank you very much for
your help with this.
Jim
On 2/12/2014 2:58 AM, Tom Evans wrote:
On Mon, Feb 10, 2014 at 10:24 PM, Jim Borland jborl...@calpoly.edu wrote:
My server, which is located in the Amazon cloud, was just moved to a new
location
On Jan 23, 2014, at 4:44 AM, Ole Kürstein okyrst...@gmail.com wrote:
I have a problem. Dont know if it can be done.
It is this i can't get working: www.example.com/test
can't get the /test working
example---
VirtualHost *:80
ServerName www.example.com
ServerAlias
On 07/10/2012 10:20 AM, Roland Roland wrote:
Can anyone help me out in understand how/why virtual host take
precedence on the same ip ?
like i always face an issue where two distinct virtual hosts are set.
the first works, the second doesn't unless i bump it up so it becomes
the first listed
On Wed, Jul 11, 2012 at 12:20 AM, Roland Roland r_o_l_a_...@hotmail.comwrote:
Can anyone help me out in understand how/why virtual host take precedence
on the same ip ?
like i always face an issue where two distinct virtual hosts are set.
the first works, the second doesn't unless i bump it
Thanks for the reply. I removed the 443 from that directive, since I'm
using standard ports, I don't think I need to specify anything. I
believe that may have been added automatically by Webmin at some point
when I was messing with it.
Here is the httpd -S output:
VirtualHost configuration:
1. What are you typing to access it?
2. Try removing the :443 from your primary ServerName entry. I believe
the port is defined inside the VirtualHost tag.
-Original Message-
From: Dennis Putnam [mailto:d...@bellsouth.net]
Sent: Sunday, March 13, 2011 1:27 PM
To: users@httpd.apache.org
On Sun, Mar 13, 2011 at 4:59 PM, Hossy hossy-apa...@hossy.com wrote:
1. What are you typing to access it?
2. Try removing the :443 from your primary ServerName entry. I believe
the port is defined inside the VirtualHost tag.
-Original Message-
From: Dennis Putnam
Davide,
Let us assume my hostnames 2287 and 2288 . How should I go about
creating a
I tried the following is it correct ?
NameVirtualHost *:80
VirtualHost *:9080
ServerName BLRD2287
DocumentRoot /www/docs/dummy-host.example.com
/VirtualHost
VirtualHost *:9081
ServerName BLRD2288
Loganathan Ramasamy wrote:
Let us assume my hostnames 2287 and 2288 . How should I go about
creating a
I tried the following is it correct ?
Nope. You should have something like:
NameVirtualHost *:80
VirtualHost *:80
ServerName BLRD2287
DocumentRoot /www/docs/dummy-host.example.com
42 matches
Mail list logo