You need to point www.inplanesight.org to the same IP as inplanesight.org.
You can also make an A record in your DNS for *.inplanesigt.org which will
act as a "catch all" for any subdomain.
On Mon, May 18, 2015 at 1:54 AM Reinis Rozitis wrote:
> > Well this looks so simple in the nginx manual.
I am moving a Drupal 7 application on Ubuntu 14.04 from development to
production. I use nginx (1.4.6-1ubuntu3.2) and php5-fpm
(5.5.9+dfsg-1ubuntu4.9).
The production machine is a VPS hosted at 1&1 and was running alright up
until about 4 hours ago. Nginx had been giving some errors on startup:
If you access it correctly, nginx will send the request to backend and pass
response which is 302-redirect-link in your case back to the browser.
Check the "302-redirect-link", I think it should be an address to
http://192.168.15.159:7090 not to nginx(port 8064/8065), that's why the
browser bypass
Well this looks so simple in the nginx manual. I have cleared the browser
cache. so I am running out of simple idea. The domain is inplanesight.org.
http://www.inplanesight.org will 404
http://inplanesight.org works fine
It's a dns problem - www.inplanesight.org doesn't resolve
http://www.dnswa
Well this looks so simple in the nginx manual. I have cleared the browser
cache. so I am running out of simple idea. The domain is inplanesight.org.
http://www.inplanesight.org will 404
http://inplanesight.org works fine
Here is the server part of the nginx.conf file:
Hello,
I would like to use Nginx as Load Balancer (traffic). My config is:
upstream storages {
least_conn;
server str1 weight=1 max_fails=1 fail_timeout=10s;
server str2 weight=1 max_fails=1 fail_timeout=10s;
}
server {
listen 80;
server_name verteilen;
J.J J wrote on Sunday, May 17, 2015 2:54 AM
>Signal handler is ngx_signal_handler which in worker process does
>nothing but log exit code and release possible holded mutexes,
>only master process reap child by setting ngx_reap to 1 and spawn
>it in ngx_reap_children if registed in ngx_processes(wo
