I've found the problem. Thank you everybody for the tip about nginx -T
The web app that I use "forge" to deploy servers seemed to add another
redirect hidden inside of /etc/nginx/forge-conf/before/ssl_redirect.conf
which was redirecting port 80 example.com to https://example.com
My server block w
Echo Arief,
Thanks for the reply.
My complete set up is below. The only difference is the use of "example.com"
instead of the domain for privacy reasons.I was really hoping that a
gracious person would just point out the mistake in the set up if there is
one...
server {
listen 80;
listen 443 ss
Thank you for the reply Francis,
I have only 1 server {} with "example.com".
I have one server block that listens on ports 80 and 443 to example.com and
redirects to https://www.example.com like this:
server {
listen 80;
listen 443 ssl;
server_name example.com ***IP Address***;
return 301 h
Thanks for the tip Francis but Nginx -T doesn't give me a clue at all.
Would you know what specifically I can change to fix this?
Thank you so much
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267700,267850#msg-267850
___
nginx mailing li
itpp2012 Wrote:
---
> Lebod Wrote:
> ---
> > Thank you for the reply;
> >
> > If we did this:
> >
> > server {
> > listen 80;
> > -li
Thank you for the reply;
If we did this:
server {
listen 80;
-listen 443 ssl;
server_name example.com ***IP Address***;
return 301 https://www.example.com$request_uri;
}
Wouldn't this stop https://example.com from re-directing to
https://www.example.com then ?
Posted at Nginx Forum:
h
location ~ /\.ht {
deny all;
}
if ($allowed_country = no) {
return 444;
}
}
I was wondering if there was an issue in our setup that's causing the double
redirect and the error:
nginx: [warn] conflicting server name "example.com" on 0.0.0.0:80, ignored
T
