SSL certificates are tied to a domain, not to physical computer. A client (browser) is not able to resolve to a physical machine. And this is a good thing! I can't imagine what will happen if clients would get information of our physicals machines even it would be the MAC address only.
The browser is able to check the domain the responses come from. Regards Lutz -- Lutz Epperlein ---------------------------------------------- Agendo Gesellschaft für politische Planung mbH Köpenicker Str. 9 10997 Berlin http://www.agendo.de/ ---------------------------------------------- > -----Original Message----- > From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Doug Hall via > 4D_Tech > Sent: Monday, October 2, 2017 5:31 PM > To: 4D iNug Technical <4d_tech@lists.4d.com> > Cc: Doug Hall <doughall...@gmail.com> > Subject: Re: NGINX Config > > 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 ********************************************************************** 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 **********************************************************************
