<garrison>
My intermittent failures in the install script were repeated `sandstorm/gateway.c++:1029: error: refused HTTPS connection because no TLS keys are configured`. I am not certain that they are related to the amount of available memory, but these failures seemed to go away when I increased to 2 GB.
<garrison>
My memory of xz running out of RAM is actually from my experience running docker-spk in a VM. It empirically requires something like 4-5 times the image size to be loaded into RAM at once. (One time I built a very large package for debugging purposes, and it failed.)
<garrison>
install script log failures (sometimes?) also include lines like "Front-end died! Restarting it..."
mnutt has quit [Quit: Leaving...]
mnutt has joined #sandstorm
<isd>
Yeah, that's a known issue with docker-spk; it builds the whole file system in memory. Fixing it requires adding a feature to go-capnproto, and at the time I figured if it were taking up enough memory to be a problem, that would mean a huge spk, so I didn't proritize it at the time. But if it's something folks have actually hit, maybe I should take the time.
<garrison>
I don't think it is that relevant, at least not now and not for me. The package I was building included an entire debug build of julia from source. It was not that hard just to remove most of it and keep only the files relevant for debugging.
<isd>
...I may just fix that anyway; it's not like it's a complicated thing to implement...
koo6 has quit [Remote host closed the connection]
AlSanc has joined #sandstorm
<AlSanc>
Hello, anyone online?
<abliss>
what's up?
<AlSanc>
Hey there, trynna install sandstorm on my domain but just cant get it work
<AlSanc>
would really appreciate any help
<ocdtrekkie>
We can try! What's going on?
<AlSanc>
I've got a digital ocean droplet going and a domain on GoDaddy. Logged into the droplet through terminal, updated it, ran the installation, and here's where I'm stuck
<AlSanc>
I put it to point to my domain, http://domain.com:6080, but can't login through the admin token
<AlSanc>
I went into the DNS records and I think I pointed everything correctly, but not sure
<AlSanc>
I suspect it might be due to wildcard CNAME. I pointed it as *.domain.com into domain.com
<AlSanc>
Not sure whether I was supposed to do something additional
<AlSanc>
I did it in both GoDaddy and DigitalOcean Networking tab
<AlSanc>
Could it be that I need a wildcard SSL certificate?
<ocdtrekkie>
So easiest way to test DNS, is to do an nslookup or ping to an address that you expect to go to your server.
<ocdtrekkie>
ping foo.mydomain.com should attempt to ping your server's IP address.
<ocdtrekkie>
If you are going to use HTTPS, you need a wildcard certificate, but Sandstorm can enroll you in those with Let's Encrypt.
<AlSanc>
honestly right now I just want to get it going, HTTP is fine
<ocdtrekkie>
Can you share your sandstorm.conf file, substituting sensitive parts? aka, example.com?
<AlSanc>
okay I did ping to domain.com, the IP is different from the one I got on digitalocean
<ocdtrekkie>
Note that you may also need a DNS entry for your main base URL in addition to your wildcard DNS entry.