@Stewart_Allen1 's awesome SSL support now in the 1.92 release of SPJS. In the screenshot below I’m connecting to SPJS over a secure websocket. You do need to specify the entire wss://yourip:8990/ws URL to get this to work.
Version 1.92 in Github release page https://github.com/chilipeppr/serial-port-json-server/releases
BTW, this also means you can now do native development in Cloud9’s preview window since they force HTTPS and that killed any clean/easy SPJS connectivity in your test/dev environment.
Very nice, I’ll test that today.
Chilipeppr is getting more and more professional. Love it.
What is surprising is the browser doesn’t complain about those sample cert and key files.
@jlauer I keep getting an ajax error when I try to use the SSL port. I thought this was just because of me doing it remote but it does the same if I use it locally. Any ideas?
Have you succeeded the way I have in the above screenshot?
Yeah for the most part. It shows the option to connect to localhost over SSL but fails to do so. The json server complains about an unknown ca cert. I tried following up on that but the only supposed solution I’ve found so far is to run update-ca-certificates after copying the cert.pem to /etc/ssl/certs but there’s still no love.
I simply renamed sample-cert.pem to cert.pem and sample-key.pem to key.pem in the same folder as SPJS.
hmm, I may try to do that but I copied the binary over to /usr/bin and call it from /etc/local.d/ to start when the system starts, and I used the appropriate commandline args so I’m not sure what the issue is. I’ll see if copying them both renamed to /usr/bin will work…if not I may have to call it manually to get it to work
It looks in the local directory by default. If you want to move .pem files to alt spaces you have to tell spjs on command line where they are. Just run spjs with -? cmd line option to see the commands.
I did that initially which is why I can’t figure out why it can’t see it.
Well this is apparently an issue with the json-server because I tried renaming the cert/key pair and calling the binary from my home directory and I get the same problem. The json server is spitting out that it’s an unknown ca certificate and that’s a known problem with Go programs so I put in a bug report in hopes it’ll get addressed.
