Nginx domain work without be into sites-enabled

[Francis Daly]

On Mon, Aug 03, 2015 at 07:41:15AM -0400, Eberx wrote:
> Francis Daly Wrote:

Hi there,

> > What response do you get for "curl -i http://music.example.com/"?
> 
> I get response header
> 
> Server: nginx
> Date: Mon, 03 Aug 2015 11:39:04 GMT
> Content-Type: text/html; charset=utf-8
> Transfer-Encoding: chunked
> Connection: keep-alive
> Vary: Accept-Encoding
> Set-Cookie: example=lda48dtiqiaqg46paqulh9ov56; path=/; domain=.example.com
> Expires: Thu, 19 Nov 1981 08:52:00 GMT
> Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
> pre-check=0
> Pragma: no-cache
> 
> Below this header our website html displayed.

Is "our website html" from music.example.com or from www.example.com or
from something else?

> > What response do you want instead for "curl -i
> > http://music.example.com/"?
> 
> I just want to go default vhost config.

What is your default vhost config?

If you want specific help, you will need to give specific details.


How nginx chooses which server{} block to use is described at
http://nginx.org/en/docs/http/request_processing.html

If you can create a config file where your nginx does not do what that
page describes, then you will have found an interesting bug.

So: in your nginx.conf, plus any file that is "include"d in there,
look at all of your server{} blocks, and in them, look at all of your
"listen" and "server_name" directives.

Then follow what that web page says, and identify which one server{} block
nginx should use to handle your request for http://music.example.com/.

Is that the server{} block that you want nginx to use?

If not, make whatever changes are needed so that it is.

Good luck with it,

	f
-- 
Francis Daly        francis at daoine.org