Very cool. Very simple to understand once you understand it. I did figure
this out on my own simply by creating more files for the WWW side of each
domain. It now works properly. Thank you.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,277674,277695#msg-277695
___
On Wed, Dec 06, 2017 at 05:27:01PM -0500, qwazi wrote:
Hi there,
> is, one of the domains on the server that has 2 isn't resolving correctly
> from the outside world. It only resolves correctly when you use just
> http://domain.com. If you use http://www.domain.com it resolves to the
> vhost1 d
I had to go back and create another conf file for the third domain as it was
now directing to the first domain if I use the WWW on it.
WEIRD! But creating another conf file works sounless you want to tell
me I'm doing it wrong, I'll leave it for now.
Posted at Nginx Forum:
https://forum.ng
I use geopeeker.com to accomplish the same thing only it renders the site so
you can see it, not just resolves the name.
I fixed the problem but I don't think it's the right way to do it. I
created a 4th conf file for just the WWW and it seems to be working
correctly now.
Posted at Nginx Forum:
First Step
Use something like http://www.kloth.net/services/nslookup.php
To check the IP addresses returned for all six names (with and without www for
the three domains)
Do these look correct?
Sent from my iPhone
> On Dec 6, 2017, at 5:27 PM, qwazi wrote:
>
> I'm new to nginx but needed a
I'm new to nginx but needed a solution like this. It's very cool but I'm a
newbie with a small problem.
I'm using nginx as a simple reverse web proxy. I have 3 domains on 2
servers. I'm using 3 files in sites-enabled called your-vhost1.conf ,
your-vhost2.conf and so on. The stand alone domain
