Re: Bouncing to Default Server Block

2018-09-28 Thread Bee.Lists
It’s fixed. Thank you > On Sep 28, 2018, at 11:48 AM, Bee.Lists wrote: > > I often clear the cache and restart nginx. Cheers, Bee ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Bouncing to Default Server Block

2018-09-28 Thread Bee.Lists
I often clear the cache and restart nginx. > On Sep 28, 2018, at 11:19 AM, Reinis Rozitis wrote: > > If you are testing just with a browser make sure you've cleaned the cache (or > disable it, or use some other tools which don't have cache (like wget for > example)). > > If by chance you op

RE: Bouncing to Default Server Block

2018-09-28 Thread Reinis Rozitis
> First domain redirects port 80 to ssl 443. > Second domain is just port 80. > Third domain is just port 80. > > Second domain isn’t showing up, pointing to first domain. Third domain is > working. Why would this happen? If you are testing just with a browser make sure you've cleaned the cache

Bouncing to Default Server Block

2018-09-28 Thread Bee.Lists
I have a test server up with 3 domains. First domain redirects port 80 to ssl 443. Second domain is just port 80. Third domain is just port 80. Second domain isn’t showing up, pointing to first domain. Third domain is working. Why would this happen? nginx.conf: # user