using zedrem in --server mode in digital ocean droplet with letsencrypt certs

[Jonathan Annett]

Has anyone got a few pointers on how to get this working?

I've created my ssl certs using the letsencrypt commandline tool and i have them up and running under node, so i know the certs are good.

they are sitting in a folder under ls /etc/letsencrypt/live/my-whatever-it-is-domain.info/ (not the real domain name) and the file it made are

fullchain.pem

privkey.pem

chain.pem

cert.pem

(node uses the first 3 as follows, if this information is helpfull for others setting up node with lets encrypt- just putting that out there)

var cert_path="/etc/letsencrypt/live/my-whatever-it-is-domain.info/"

var httpsOptions = {

    key: fs.readFileSync(cert_path+'privkey.pem'),

    cert: fs.readFileSync(cert_path+'fullchain.pem'),

    ca: fs.readFileSync(cert_path+'chain.pem')

};

anyway back to zedrem....

i edited my ~/.zedremrc as follows (again not the real ip address or domain name) 

[client]

url = wss://1.2.3.4:7337

userKey = youruserkey

# For running zedrem in server mode

[server]

ip = 1.2.3.4

port = 7337

sslCert = /etc/letsencrypt/live/my-whatever-it-is-domain.info/fullchain.pem

sslKey = /etc/letsencrypt/live/my-whatever-it-is-domain.info/privkey.pem

when i start up the server instance (using ./zedrem --server) it seems to start ok and gives me a url which is the same one i edited into the [client] section above

when i start the client it the server says this: (id is redacted)

Client 42437*******653dd connected
Client disconnected 42437*******653dd

and the client says this:

A Zed window should now open. If not, make sure Zed is running and configured with the correct userKey.
Press Ctrl-c to quit.
ERROR: Your Zed editor is not currently connected to zedrem server wss://1.2.3.4:7337.
Be sure Zed is running and the project picker is open.

now in the chrome app (zedapp) when i try to connect using remote folder it won't accept the wss:// url and if i change it to https:// it says it's invalid. with http:// it appears to work, but the server starts complaining about TLS handshakes being incorrect

i am thinking there is something i am missing in terms of configuration in the chrome app, or perhaps i am using the incorrect certificates?

i saw a very old post talking about a server config in the chrome app, but i can't find anything resembling that in the current version.

i really can't use the product via the zedrem servers and need to have a secure solution standalone.

any help would be appreciated.