> Both did the trick, but which one is better?
I personally prefer the $request_uri one because it’s very clear exactly what
it does.
> I think I read somewhere that nginx would connect unencrypted to the backend,
> and do the encryption / decryption, is this wrong then?
Nginx will connect
Thank you so much for your time!!
Best regards
Danjel
From: Lucas Rolff
To:"nginx@nginx.org"
Subject: Re: reverse proxy https not working
Date sent: Sun, 26 Aug 2018 11:42:48 +
Send reply to:
Which functions do not work?
Be aware some software (WordPress being a good example) doesn’t always work
with reverse proxies that easy.
Could you possibly include your nginx configuration? Especially your proxy
parts.
From: nginx on behalf of "Jungersen, Danjel -
Jungersen Grafisk ApS"
From: Lucas Rolff
To:"nginx@nginx.org"
Subject: Re: reverse proxy https not working
Date sent: Sun, 26 Aug 2018 08:19:28 +
Send reply to: nginx@nginx.org
> Which functions do not
Hi there.
I have a setup that almost works.
:-)
I have a handful of domains that works as they should.
Traffic as accepted and forwarded to my apache on another server (also in dmz).
I have setup certificates with certbot.
I have green (encrypted) icon on my browser when I visit my sites.
> The vendor recommended me to use a reverse proxy
Ideally the vendor should have a working config in that case, but, I do see a
few things that can be an issue.
You’re serving https but proxying to an http backend – depending on how the
software works, a lot of the reverse URLs that is
Thanks !!!
proxy_pass https://192.168.1.3;
proxy_pass https://192.168.1.3$request_uri;
Both did the trick, but which one is better?
I will now try to re-enable all the "force encryption" settings.
And closing firewall ports to see what I can avoid having open.
I'm a bit of novice
