too many redirects

JACK LINKERS jacklinkers at gmail.com
Fri Nov 21 08:02:01 UTC 2014


Hi guys,

This is not the first time I use this mailing list for support and it has
always been very helpful.

I might have forget to tell I'm using ISPConfig to setup my vhosts
The .conf file is automaticaly generated, I only add some tuning to make
different things work such as WordPress, PrestaShop, PageSpeed and so on.

When I say i'm completely lost, I mean there is indeed plenty tutorials on
how to set up a vhost manually and each tutorial is different (almost).

You are right when you say something may work on some setup and not on
mine, because it's not a part of a whole thing.

I'll read everything you posted and try to figure out how to combine it
with default vhost template in ISPConfig, because everytime I reload the
server all changes made directly in vhost .conf files is rewritten with
defaults.

On ISPConfig admin panel, I have an "Option" Tab where I can add custom
nginx directives. All these directives are added at the end of the vhost
.conf file. This is the only way I have in order to have my custom
directives saved even after a reboot.

For now, I need to fix my idividual vhost and then try to modify the vhost
template from ispconfig.

As you can see, the template doesn't make separate server blocks for each
HTTP & HTTPS protocole :

http://pastebin.fr/37523

And once again, thanks for your time / patience / help.

Regards

2014-11-21 1:09 GMT+01:00 Francis Daly <francis at daoine.org>:

> On Thu, Nov 20, 2014 at 10:07:22PM +0100, JACK LINKERS wrote:
>
> You probably already have the answer now, but just in case not...
>
> > I completely lost...
> > I tried everything (of my understanding) with no success.
>
> Your original config was:
>
>  listen on http and https; redirect everything to https.
>
> That's a recipe for an infinite loop, as your browser reported.
>
> What you probably want is:
>
>  listen on http; redirect everything to https.
>  listen on https; process requests normally.
>
> which is most easily done with two separate server{} blocks.
>
>         f
> --
> Francis Daly        francis at daoine.org
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20141121/948d79d9/attachment.html>


More information about the nginx mailing list