kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Public logs at https://botbot.me/freenode/sandstorm/
_whitelogger has joined #sandstorm
ss-ssl has joined #sandstorm
<ss-ssl> Hello again. My sandstorm setup was working fine until I moved to NGINX with a reverse proxy to support SSL. Now SSL works but I am getting the yellow warning message on Admin page regarding "WILDCARD_HOST" being misconfigured. The browser console states "Sandstorm WILDCARD_HOST self-test failed. Details: Error: Connection lost" and "Failed to load
<ss-ssl> resource: net::ERR_CERT_COMMON_NAME_INVALID". The issue seems to be due to my wildcard SSL supporting *.domain and not *.subdomain.domain. I tried setting it up with sandstorm-*.domain but unable to add appropriate A/CNAME record on Godaddy's DNS. Please advise?
_whitelogger has joined #sandstorm
<xet7> ss-ssl: You need to get new SSL cert for your *.subdomain.domain, for example a) free cloudflare cert b) Let's Encrypt wildcard c) Buy that SSL cert. Or alternatively, use Sandstorm at *.domain .
<xet7> ss-ssl: Let's Encrypt wildcard updates need to modify DNS records when updating cert, probably CertBot may support that.
<xet7> ss-ssl: Other option is to move back to using sandcats.io domain
<xet7> ss-ssl: If you are unable to make required changes at Godaddy's DNS, you can change your servers for example to CloudFlare, and try making changes there.
<xet7> ss-ssl: I mean your nameservers
<ss-ssl> thanks, I set the DNS to *.domain.tld and modified sandstorm config to use sandstorm-*.domain instead of *.sandstorm.domain. So far looks fine, will test more tomorrow.Thanks for your help!
<xet7> ss-ssl: Thanks for thanks :)
Zarutian has quit [Read error: Connection reset by peer]
Zarutian has joined #sandstorm