xet7_ has quit [Remote host closed the connection]
xet7_ has joined #sandstorm
xet7 has quit [Ping timeout: 240 seconds]
xet7_ is now known as xet7
xet7 has quit [Remote host closed the connection]
bb010g has joined #sandstorm
larjona has joined #sandstorm
xet7 has joined #sandstorm
xet7 has quit [Quit: Leaving]
xet7 has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
griff__ has joined #sandstorm
<JacobWeisz[m]>
vagrant-spk 1.1.1 is released. It only matters to Windows users though.
griff__ has quit [Quit: griff__]
xet7 has quit [Quit: Leaving]
xet7 has joined #sandstorm
NekoIncardine has quit [Read error: Connection reset by peer]
fkautz has quit [Read error: Connection reset by peer]
jimpick has quit [Read error: Connection reset by peer]
NekoIncardine has joined #sandstorm
jimpick has joined #sandstorm
fkautz has joined #sandstorm
ecloud_ has quit [Read error: Connection reset by peer]
ecloud has joined #sandstorm
xet7 has quit [Remote host closed the connection]
oddhack has joined #sandstorm
<oddhack>
Hi, I am trying to get Sandstorm self-hosted running on a Digital Ocean Ubuntu droplet. The install script all goes OK until it tries to obtain a Lets Encrypt certificate, when it hangs and then eventually errors out. Is this a known issue? Am I trying to do something that just isn't going to work? Any tips graetfully received - thanks
<JacobWeisz[m]>
As far as I know it should work.
oddhack has quit [Quit: Connection closed]
<JacobWeisz[m]>
Are you getting any sort of error message? I'm assuming you are trying to set up with a Sandcats... oh, they gone.
oddhack has joined #sandstorm
<oddhack>
It's not clear to me from the log which exact error is happening, but I think it might be this one: "error: refused HTTPS connection because no TLS keys are configured"
<JacobWeisz[m]>
I am kind of curious how far installed Sandstorm is, sometimes Let's Encrypt just takes a bit.
<JacobWeisz[m]>
If Sandstorm is done installing, I wonder if you restart the service if it will get it's certificate properly.
<oddhack>
hmm that's worth me checking - I assumed not installed because of the error message but maybe it is!
<JacobWeisz[m]>
If you were local to the box, you could presumably connect over HTTP and configure Let's Encrypt from the web UI, but that's not preferable in the case of a DO droplet. There are some CLI commands we can try to instruct the TLS configuration if it is installed but TLS isn't properly set up.
<oddhack>
sandstorm service is running!
<oddhack>
have restarted
<JacobWeisz[m]>
Also, is there anything you need to do on DO to open up your HTTPS port to the Internet or anything? It's a common place to get stuck with AWS instances in particular, and I've never used DO personally.
<oddhack>
maybe - I'm new to it, will have a look. thank you for your advice. There is nothing currently available at the *.sandcats.io URL I selected
<JacobWeisz[m]>
Does pinging your Sandcats address return the IP of your droplet?
<oddhack>
yep!
<oddhack>
this is looking promising
<JacobWeisz[m]>
So Sandcats is registered to your server and knows your IP, Sandstorm is installed, and ideally should be correctly configured. If it's still not reachable, we probably want to look at your sandstorm.log to see if it's still unable to get a certificate.
<oddhack>
gotta go to bed now - will look again tomorrow. thx again