I have a domain.com and i can redirecto to other subdomains but not
domain.com in https, my configuration is the following :
server {
listen 80;
server_name www.domain.com;
rewrite ^/(.*) https://www.domain.com/$1 permanent;
}
server {
listen 80;
server_name m.domain.com;
The problem is https://domain.com is not accessible
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256099,256100#msg-256100
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Isn't this ?
server {
listen 443 ssl spdy;
server_name domain.com;
...
}
With that configuration if a go https://domains.com it gives me a error
webpage not avaiable
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256099,256102#msg-256102
It is a DNS (not a Nginx) problem. It seems that you have different IN A
records for domain.com www.domain.com
On Wed, Jan 14, 2015 at 1:46 PM, ramsoft75 nginx-fo...@nginx.us wrote:
I made a ping into www.domain.com and into domain.com, the Ip's are not
the
same.
Posted at Nginx Forum:
I made a ping into www.domain.com and into domain.com, the Ip's are not the
same.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256099,256104#msg-256104
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Am Mittwoch, 14. Januar 2015, 04:34:34 schrieb ramsoft75:
I have a domain.com and i can redirecto to other subdomains but not
domain.com in https, my configuration is the following :
server {
listen 80;
server_name www.domain.com;
rewrite ^/(.*)
On 14/01/2015 10:30, ramsoft75 wrote:
Isn't this ?
server {
listen 443 ssl spdy;
server_name domain.com;
...
}
With that configuration if a go https://domains.com it gives me a error
webpage not avaiable
I'm guessing the above is a typo in the mail and that you're not
actually trying
