ChanServ changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things Sandstorm and Cap'n Proto. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Channel logs available at https://libera.irclog.whitequark.org/sandstorm
<blowfist> When adding the CNAME and TXT records to the DNS to link to a sandstorm static HTTP share, is there some special configuration to add to nginx to make that work? It just won't seem to work for me.
<ocdtrekkie> I don't think so but I don't use Nginx in front of my Sandstorm
<blowfist> ocdtrekkie: any clues what could be my issue?
<blowfist> the CNAME and TXT records show correctly when I query them from another system
xet7 has quit [Remote host closed the connection]
<ocdtrekkie> Do you get anything on the page when you go to the CNAME in the browser?
<blowfist> I get the placeholder index.html I set up in nginx for the domain
<blowfist> I have a server entry for that domain so the TLS certificates are used and put a placeholder index.html on the root location
<blowfist> like : location / { root /path/to/static/domain/index.html }
<blowfist> if I remove that part I get a 404
<blowfist> it doesn't seem to ever connect to sandstorm
<blowfist> now if use a reverse proxy connecting to the sandstorm connection, it all works but that would be a total bypass of the CNAME record
<ocdtrekkie> Generally the TXT record setup is assuming the entire wildcard space as defined in WILDCARD_HOST is directed at Sandstorm
<ocdtrekkie> So you should always see a Sandstorm error message when accessing a subdomain within that wildcard.
<ocdtrekkie> Like if you view the URL you're setting as the destination of your CNAME, do you see the static published site?
<blowfist> yes, that works fine
<blowfist> do note that the domain I'm attempting to use is a different one from the one used for my sandstorm instance
<ocdtrekkie> Right, it should be.
<ocdtrekkie> If the URL the CNAME points at works and the text record is right... it should work AFAIK.
<blowfist> well I'm guessing it's a nginx issue
<blowfist> someone on a forum said that the CNAME record is used strictly to get the IP address and then call that IP with the original domain name...
<blowfist> if this is the case, then no wonder it would not work
<blowfist> nginx would get a request for the original domain rather than the sandstorm link
xet7 has joined #sandstorm
<blowfist> ocdtrekkie: was this tested with nginx?
<ocdtrekkie> A reverse proxy with Nginx in front of Sandstorm used to be a very common setup, so I would be shocked if it was not.
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm