Web App not accepting secure connections

Anybody have experience getting a web app to allow SSL connections? I found the tutorial from 2014.
I opened up the port (8081) on my server’s firewall.
I grabbed the cert from my apache install and copied it next to the web app’s executable.
I launch the web app with flags: --secureport=8081 --maxsecuresockets=400 --logging

And my web browsers just say they can’t connect; the connection is immediately terminated.
I then tried to make my own self-signed cert. Moved it next to the web app executable. Same deal.

Chrome’s response:
This site can’t be reached
The connection was reset.

Safari’s response:
Safari can’t establish a secure connection to the server …

The “apache style logging” shows no connection attempt.
Server is 64-bit CentOS.
IDE: 2017r3

As a sanity check I made a console app and listened on port 8081 for secure connections. The browsers timed out; the connection wasn’t immediately dropped.

Excuse me if it seems a dumb question, but are you accessing the app using “www.yourdomain.com:8081/

Is this the tutorial you’re following? (for standalone web apps? http://developer.xojo.com/standalone-ssl

Javier

Make sure you grabbed all three pieces, the cert, the intermediates and the key. SSLSockets need all three pieces to make a secure connection.

[quote=374455:@Javier Menéndez]Excuse me if it seems a dumb question, but are you accessing the app using “www.yourdomain.com:8081/
Javier[/quote]

Correct - the standard SSL port is 443, so if you are using an alternative port you’ll have to include both the protocol (HTTPS) as well as the port, like this:

 https://example.com:8081/

Also, is the port opened in the firewall? (CentOS) enables almost everything after install it.

*** SORRY *** I’ve just read you opened it ***

[quote=374455:@Javier Menéndez]Excuse me if it seems a dumb question, but are you accessing the app using “www.yourdomain.com:8081/

Is this the tutorial you’re following? (for standalone web apps? http://developer.xojo.com/standalone-ssl

Javier[/quote]

I was following the original blog post from 2014.

Greg,

From LetsEncrypt’s readme:

So I tried fullchain. I tried converting pem to crt. I also tried just copying the file over.

What’s the magic mojo?

I tried making a self-signed cert with openssl, too.

I had to merge fullchain.pem & privkey.pem into one file. Thanks Greg!