RE: Note if you enable 443 and ssl for any server you must have a cert for
all
servers listening on 443 you cant mix them up.
We only have the one physical server (running 4D in remote mode). You
aren't talking about the different domains being served from that one
machine are you? SSL certificates are tied to the physical server
(computer), not nginx server block/domain name, right?
Thanks,
Doug
On Mon, Oct 2, 2017 at 1:49 AM, Paul Dennis via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Hello Jason,
>
> I ve been doing this for years my config is simpler. Dont understand why
> you
> need to define the upstream and rewrite for a simple proxy. I just have a
> server block (nginx jargon) as follows.
>
> server {
> listen 443 ssl;
>
> server_name dashboard.xxx.com;
> client_header_buffer_size 2k;
> large_client_header_buffers 8 12k;
> client_max_body_size 20m;
> ssl_certificate
> /etc/letsencrypt/live/dashboard.xxx.com/fullchain.pem;
> ssl_certificate_key
> /etc/letsencrypt/live/dashboard.xxx.com/privkey.pem;
>
> location / {
> proxy_pass http://192.168.1.20:8086/;
> }
>
>
> Note if you enable 443 and ssl for any server you must have a cert for all
> servers listening on 443 you cant mix them up.
>
>
>
>
>
>
> --
> Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ: http://lists.4d.com/faqnug.html
> Archive: http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************
>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
