Re: RE: RE: Two domains and multiple server blocks
You are absolutely rightI'm feeling like an idiot, really! For weeks I've tried to change every single character in nginx configuration and your first tip to look at the request header was worth the number of characters in gold ;) wsc is indeed the default prefix for Woltlab Suite and indeed, the first configuration was with the sub domain and not the standalone domain. I am sorry to wrongly suspected Nginx to be the source of this problem and appreciate your help very much, it really killed a lot of sleep time. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276031,276041#msg-276041 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
RE: RE: Two domains and multiple server blocks
> But the problem still remains and it is getting weirder with every minute.'' I'm not familiar with WoltLab Suite but it feels that it does the same as Wordpress as in it forces redirects to the domain the application is configured. Could it be that you configured it initially on the 3jgkp.de domain? For example you can open http://armapedia.de/images/lato/armapedia.png just fine without redirect. Also if you request http://armapedia.de/somepath it gets redirected to http://armapedia.3jgkp.de/?somepath (which is clearly something based on your provided nginx configuration is not supposed to do) p.s. one thing to note is that at least the IP you provided (and the domain resolves to) actually doesn't listen on 443 (https) port (unless it's not specifically disabled in firewall it's not public). rr ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: RE: Two domains and multiple server blocks
Thank you Reinis for the tip with the outdated version of Nginx, now I am using 1.12 ;) But the problem still remains and it is getting weirder with every minute. Even if I disable the 3jgkp.conf completely so only one server block remains, armapedia.de will be redirected to armapedia.3jgkp.de. Maybe that is because of the cookie you mentioned earlier, but I have no clue how to delete this information or where this magic redirection is coming from. Can this be a problem of my DNS configuration? Otherwise, I ran out of any option left to try or to look into... Posted at Nginx Forum: https://forum.nginx.org/read.php?2,276031,276039#msg-276039 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
