I am following this guide: https://docs.xojo.com/UserGuide:SSL_for_Standalone_Web_Apps
I have successfully received a cert using Let's Encrypt, and have then concatenated the fullchain1.pem and privkey1.pem files into "myapp.crt"
I then run my web app on Ubuntu with this cmd:
./myapp --secureport 9001 --certificate /somepath/myapp.crt
I made sure the path to the cert file is correct. Yet, when I try to connect to the app with https on port 9001, the Browser says that it can't establish a connection, i.e. it gets a rejection immediately, and it's not a secure attempt, even. Also, I log when Session.Open gets invoked - and that does not happen. So, it looks like my app does not actually listen on port 9001 at all.
And indeed - when I check with
lsof -i -P -n | grep LISTEN, I see that the app's regular port (9000) is in LISTEN mode, but there's no open port for 9001.
So, the app simply does not listen on the SSL port. Why?
I then tried this to see what happens:
./myapp --secureport 9001 --certificate /badfile.crt
Which means: I pass the path to a nonexisting crt file.
The docs say:
If you try to start with SSL but the certificate is not found or is not readable, the app will display an error and quit.
Well, that's not happening - despite passing an invalid cert file, I get no message (on the cmdline) nor does the app quit.
So, something is wrong here, but what?
I'm trying this with Xojo 2019r1