Clojurians Log v2

> How long has it been since you pointed your domain to digitalocean's nameservers? It can take a little while for the change to take effect. it would have been wed night, so about 30 hours, still under the max. > You should be able to ssh into the droplet since it has your public key. is that how you got in? yep. > standalone in prod does standalone mean its using an in memory database? > What output do you get if you run this on the droplet?

root@biff-webserver:~/snap# systemctl stop biff
root@biff-webserver:~/snap# sudo -u biff /home/biff/run-as-biff.sh 
Agent pid 320659
Error loading key "/home/biff/.ssh/id_rsa": invalid format
sed: can't read deps.edn: No such file or directory

if i copy paste my deploy-key (private key) to the server over top what seems to be the same key i dont get invalid format. Though the rest of the errors persist.

Hypothesis: the private key isn't copied sufficiently for the setup in some way thats not detectable. Potentially not consistently reproducible. The other issues is that ./run-as-biff is running as biff which doesn't find the .ssh/id_rsa because biff not root has that. Im running run-as-root and its downloading my github files. And were live: http://urbardner.com/ 🎉

and were down 🙂. I need to have some long lived process that restarts turn the server on. Probably have to re apply/deploy

The deploy-key is used to ssh in and so needs to be copied to the ~/.ssh folder. I just did this and it let me ssh to the droplet (which i lost after i updated my key).

I think two things happened. 1. the deploy-key was misformated on transfer as evidenced by the fact that copy pasting said key manually fixed an invalid format error. 2. The deploy-key needs to be copied a users ~/.ssh folder so it can be used to ssh in. i'll turn that into a ticket if it seems reasonable. Is the latter in any way disputable? The first thing is questionable though. It make take someone else running into it to be sure.

> does standalone mean its using an in memory database? No, it means storing the entire database on the local filesystem. > sed: can't read deps.edn: No such file or directory oops, I should've had you run cd /home/biff before sudo -u biff /home/biff/run-as-biff.sh > The key in ~/.ssh/authorized keys is the "ssh-public-key" which wasn't what I had stored in github. I went ahead and added that. still get invalid format. However, thats not the public key for deploy-key, so thats likely a mismatch. This is expected. authorized_keys contains your personal public key, which allows you to ssh into the droplet. on the server, id_rsa is the private key for the deploy key which is separate, and the public key for the deploy key goes in github (so what you already did is correct). > if i copy paste my deploy-key (private key) to the server over top what seems to be the same key i dont get invalid format. > Hypothesis: the private key isn't copied sufficiently for the setup in some way thats not detectable. Potentially not consistently reproducible. very interesting... I'll keep an eye out for this > And were live: http://urbardner.com/ awesome! it looks like the letsencrypt certificate didn't get set up though. it likely failed earlier, and the way I have it run is brittle. if you rm /home/biff/certbot-ran on the droplet and then systemctl restart biff, it should provision a certificate, then your site will be available on https (and http requests will get redirected to https) > I think two things happened. > ... Agree with your assessment on #1. #2 is unnecessary--as I mentioned, the deploy key is just needed by the droplet to clone your git repo, whereas your personal ssh key is used to ssh in. The only reason you were able to ssh in using the deploy key is because of this: "I added the deploy-key-pub key to ~/.ssh/authorized keys ..."

thanks for your patience in going through this whole process 🙂 I think my main takeaway is that I need to add more error checking/failure case handling during the deploy process. e.g. check the ssh keys, handle failed certificate provisioning, make sure that prerequisite ./task commands have been run, etc. I'm planning to work on this some time next week