asheesh changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Channel glossary: "i,i" means "I have no point, I just want to say". b == thumbs up. | Public logs at https://botbot.me/freenode/sandstorm/ & http://logbot.g0v.tw/channel/sandstorm/today
xet7_ has quit [Ping timeout: 244 seconds]
decipherstatic has joined #sandstorm
dwrensha has joined #sandstorm
pie_ has quit [Ping timeout: 250 seconds]
wolcen_ has quit [Ping timeout: 250 seconds]
wolcen has quit [Ping timeout: 252 seconds]
pouledodue has joined #sandstorm
jemc has joined #sandstorm
decipherstatic has quit [Ping timeout: 244 seconds]
pouledodue has quit [Quit: Textual IRC Client: www.textualapp.com]
bemasc has quit [Ping timeout: 250 seconds]
bemasc has joined #sandstorm
jemc has quit [Ping timeout: 244 seconds]
isd has joined #sandstorm
<JonTheNiceGuy[m]> Xia0ben sorry about that, I fell asleep!
isd has quit [Quit: Leaving.]
frankier has quit [Ping timeout: 244 seconds]
sydney_u1tangle has joined #sandstorm
sydney_untangle has quit [Ping timeout: 244 seconds]
Telesight has joined #sandstorm
afuentes has joined #sandstorm
pie_ has joined #sandstorm
n-a-m-e has joined #sandstorm
n-a-m-e has quit [Client Quit]
jemc has joined #sandstorm
jemc has quit [Ping timeout: 240 seconds]
jemc has joined #sandstorm
wolcen has joined #sandstorm
wolcen has quit [Ping timeout: 276 seconds]
<digitalcircuit> I noticed grain sizes are now shown in Sandstorm. This'll help with seeing where spaces goes; thanks!
nwf has quit [Read error: Connection reset by peer]
nwf has joined #sandstorm
jdenz has joined #sandstorm
<jdenz> Hi all. I'm trying to sign in with email on my self-hosted Sandstorm instance and am getting an "Internal server error." All was working fine yesterday. Just wondering if there were changes recently or if I should troubleshoot this on the host side.
<dwrensha> jdenz: eek!
<dwrensha> we did just upgrade the mail sender
<dwrensha> jdenz: I would debug by looking at /opt/sandstorm/var/log/sandstorm.log
<jdenz> ok, thanks.
<jdenz> It's showing: Exception while invoking method 'createAndEmailTokenForUser' Error: Hostname/IP doesn't match certificate's altnames: "Host: mail.xxxx.com. is not in the cert's altnames: DNS:*.mail.yyyy.com, DNS:mail.yyyy.com"
<jdenz> dwrensha: I don't know how to solve this problem. Any hints? :)
jemc has quit [Ping timeout: 260 seconds]
<dwrensha> jdenz: is there more info with the error, like maybe a stack trace?
<jdenz> dwrensha: Yes. Here it is:
<jdenz> at Object.Future.wait (/programs/server/node_modules/fibers/future.js:449:15)
<jdenz> at rawSend (imports/server/email.js:75:5)
<jdenz> at smtpSend (imports/server/email.js:66:44)
<jdenz> at send (imports/server/email.js:164:3)
<jdenz> at sendTokenEmail (server/accounts/email-token/token-server.js:207:3)
<jdenz> at _createAndEmailTokenForUser (server/accounts/email-token/token-server.js:259:3)
<jdenz> at [object Object].createAndEmailTokenForUser (server/accounts/email-token/token-server.js:278:18)
<jdenz> at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1711:12)
<jdenz> at packages/ddp-server/livedata_server.js:711:19
<jdenz> at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
<jdenz> - - - - -
<jdenz> at Object.checkServerIdentity (tls.js:186:15)
<jdenz> at TLSSocket.<anonymous> (_tls_wrap.js:1023:29)
wolcen has joined #sandstorm
<jdenz> Sorry, this may be easier to read: http://pastebin.com/jeWR3Zs5
<dwrensha> jdenz: hm. I wonder if the problem has to do with https://github.com/sandstorm-io/sandstorm/pull/2376
<dwrensha> are you using sandcats?
<jdenz> dwrensha: Yes, I'm using sandcats.
wolcen has quit [Ping timeout: 265 seconds]
<dwrensha> cc asheesh kentonv
<jdenz> I feel like this is an email hosting issue from my email provider. I'm using a domain name I have as the email host but it's not matching the domains listed in the email host's certificate. I may be able to solve this by changing the SMTP settings in Sandstorm. Is there a way I can do this from the CLI?
<dwrensha> you could do `sandstorm mongo` and then edit the "settings" collection
<dwrensha> {"_id" : "smtpConfig"} is the row you'd want to update
<jdenz> dwrensha: I'm not familiar with MongoDB Shell. Do you know the command to update that?
<dwrensha> e.g. `db.settings.update({_id: "smtpConfig"}, {$set: {"value.hostname": "smtp.mailgun.org"}})`
<jdenz> Thank you!
<dwrensha> to see the current value, `db.settings.find({_id: "smtpConfig"})
<dwrensha> `
<jdenz> Ok, great. That fixed it.
<jdenz> dwrensha: Thank you for your help with this!
jparyani has quit [Ping timeout: 240 seconds]
<dwrensha> so what was the problem?
jparyani has joined #sandstorm
<dwrensha> oh, right you explained a bit about it above
<jdenz> dwrensha: Right. I'm not sure why this wasn't an issue before. Maybe there's a setting in nodemailer to ignore those kinds of errors?
<dwrensha> :shrug:
<dwrensha> yeah, I suspect our changes last week made some things more strict
<jdenz> Is it trivial to show a more descriptive error message when this happens?
<jdenz> Without having to check the log, that is.
garrison has quit [Remote host closed the connection]
garrison has joined #sandstorm
garrison has quit [Changing host]
garrison has joined #sandstorm
<dwrensha> I think it might be problematic to show server-side stack traces to anyone who tries to log in
<jdenz> Oh, yeah. True.
xet7__ has quit [Quit: Leaving]
<jdenz> All is working well now, so I appreciate you being available. I continue to be impressed and satisfied with Sandstorm, so thank you all for that!
<dwrensha> :)
xet7 has joined #sandstorm
<kentonv> jdenz: If I understand correctly, the problem is that your SMTP server was responding to STARTTLS with a certificate that didn't match the host?
<jdenz> Yes, that seemed to be the problem.
<kentonv> it's possible we weren't even using STARTTLS before... I'm not sure what the old library supported
<kentonv> though even if we were using it, historically people have been lax about certificate checking with SMTP because so many servers are misconfigured
<jdenz> Ok, yeah, that may explain it.
<jdenz> It's happened to me before with this email provider on other web apps I configure.
<kentonv> btw another way you could have reached the admin settings to fix this would have been with "sudo sandstorm admin-token"
<kentonv> for future reference
<jdenz> Yeah, ok, thanks.
afuentes has quit [Ping timeout: 276 seconds]
<asheesh> I guess we should s/"Internal server error"/ s
<asheesh> I guess we should s/"Internal server error"/"Internal server error; view details in the logs panel of the Sandstorm admin settings"/
<jdenz> asheesh: I would've found that helpful in this case.
<jdenz> :)
xet7 has quit [Quit: Leaving]
xet7 has joined #sandstorm
Telesight has quit [Quit: Leaving.]
jemc has joined #sandstorm
awans has joined #sandstorm
awans has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
jemc has quit [Ping timeout: 265 seconds]
jdenz has left #sandstorm [#sandstorm]
isd has joined #sandstorm
isd has quit [Quit: isd]
frigginglorious has joined #sandstorm
isd has joined #sandstorm
awans2 has joined #sandstorm
<awans2> hey y'all, question for the group:
<awans2> i'm trying to get a HackSessionContext from a golang binary, but can't seem to open /tmp/sandstorm-api
<awans2> (i'm using the http bridge)
<awans2> and indeed, vagrant-spk enter-grain would suggest the file /tmp/sandstorm-api is not present
<awans2> (asheesh told me i should use hacksessioncontext so :p)
<asheesh> hi awans2
<asheesh> weird awans2 lemme see
<asheesh> I'm currently experiencing my own weird app creation bugs.
<asheesh> Well, at least difficulties.
<asheesh> I don't see it in enter-grain either!
<asheesh> kentonv: Any reason you can think of that /tmp/sandstorm-api would be ENOENT?
<awans2> fwiw i'm running this on virtualbox vagrant on a mac
<awans2> idk if there's anything weird about unix sockets on virtualbox or sth
<asheesh> I don't think there is.
<asheesh> I'm VirtualBox + Linux fwiw
<awans2> are there any additional logs i could dig up for y'all to take a look at?
<asheesh> I can't tell yet if it's a bug in vagrant-spk enter-grain, or an actual problem.
<asheesh> The first thing I'm going to do is try to run Davros, whose static publishing support relies on /tmp/sandstorm-api actually existing.
<awans2> fwiw my golang process gives the same error
<asheesh> Davros seems to work OK for me. Hmm.
<asheesh> I have 100% no idea, I'm afraid. dwrensha does ^ ring any bells for you?
<asheesh> I can't get my requests to even route through sandstorm-http-bridge
<asheesh> awans2: BTW I think the tutorial has a bug w/r/t what one puts in "actions", but then again this bug doesn't seem to be biting you.