it’s for a server on a private network, so I’m using a self-signed certificate
done with the instructions on the above link.
seems to work I have my webapp.crt file I put in the same folder as the webapp.
I launch ./webapp --secureport=(mysslport)
and I can connect using http (and the provided http port)
but can’t connect with https and the secure provided port. it says “connexion refused”
Are you specifying the path of your crt and key? Is the port you are using open and not “occupied” by something else? Are you specifying the used port in your url, in case it is not the standard port 443?
I’ve been doing this: Simply merge all certificates (private key and intermediates) into a single file (it’s just text) and name it .crt [I put the intermediates first, then the private key, but I don’t know if the order matters). Then launch the app with the --certificate= option. Works great
thanks Mike.
do you need the --secureport option or not ?
the secureport is specified in the shared items section of the project
do you need to specify it again in the command line ?
also does it work if you omit the --certificate option and put the crt file just beside the webapp and the same name as the app ?
it’s still weird that there is only a laconic message “application is ready” and no error message if something is wrong …
couldn’t find any simple “how to” get a certificate from let’s encrypt.
easy when it’s pre-build in some servers or nas
never understand how to get one from the command line…
i use a build step to copy the .crt file beside the exe.
i also set the ssl port in shared/build propertys.
i use a “free” (one click a month) dyn dns from no-ip.com
and a self sign signed certificate for a web app that i use by my own.
i forward this secure port in my router.
the web service i run at windows in a user context for file access.