Thanks Chuck, As is obvious, I'm not an experienced admin, but a developer. I picked another unused port, 447, and tried again. I'm not running Tomcat as root. I want to get the self signed cert working before purchasing an SSL certificate.
This WORKED. Thanks for all the help. Note that I just picked an unused port at random, not knowing any better. I'm sure that there is a more sophisticated way to pick a port to use. I'm guessing that if I have Tomcat grab that port it will keep it while it is running. But for now I'm over-joyed, Don On Wed, Sep 27, 2017 at 1:24 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Don Flinn [mailto:fl...@alum.mit.edu] > > Subject: Re: Trouble using SSL with Tomcat 9 > > > I installed a new download of tomcat 9, established one application with > > php/java bridge (need php and java access). Set the SSL port to an unused > > port, 443, and ran my app who's only out put is an H1 message. This time > I > > get the expected error from Chrome with the red warning about bad > > certificate. However, the redirect went to https://localhost/Financial/ > > index.php - i.e. NO port number and of course drilling down couldn't find > > my app which is at port 443, I believe. > > Port 443 is the standard HTTPS port, so it won't show up in the https: URL > since it's the default. > > Unless you're running Tomcat as root (a very, very bad idea), you'll need > to > use iptables or equivalent to let Tomcat listen on port 443. > https://wiki.apache.org/tomcat/HowTo#How_to_run_ > Tomcat_without_root_privileg > es.3F > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > >
