14:28 <sadsand> hey, not long ago my sandstorm server completely crashed due to a kernel panic. at the moment I was trying to edit a Wekan-Grain.

14:29 <sadsand> I restartet the server and now I only get a "loading" on a white canvas, when I try to open a grain. even with a "collection" grain..

14:30 <sadsand> As well it seems as if I cannot access the App Market, nor the admin panel

14:37 <sadsand> It got better now, admin panel and app market work; grains are still problematic. I'm not sure if I should play in the backup of the server 1hour ago, to be sure..

14:42 <sadsand> a warning I get is: Warning: SandstormPermissions.grainPermissions() took 867 milliseconds to complete for the vertex

14:48 <xet7> sadsand: It would be easier if you tried some working backup

14:48 <xet7> much less to fix

14:48 <xet7> you could first try to update sandstorm on command line

14:48 <xet7> if it helps

14:57 <sadsand> i think at first we would need to know, what exactly caused the panic, no? Then we could decide, if there is some real damage and even after backing up, a fix might be needed..

15:09 <xet7> sadsand: There was broken sandstorm update

15:10 <xet7> updateing sandstorm could fix it

15:10 <xet7> or not

15:35 <sadsand> I already had the issue with the broken update and downgraded to 214 I believe... that should not be the reason

15:52 <xet7> Hmm, I don't know about is it related to kernel version bug of Sandstorm https://github.com/wekan/wekan-maintainer/wiki/Building-Wekan-for-Sandstorm

15:53 <xet7> Using specific kernel is required for me building Wekan for Sandstorm, but I don't know is it required also for using Sandstorm

21:01 <fruitytooty707> Hey guys, I'm having an issue with the setup portion. I setup Github as a login provider and when I try creating and admin account I authorize my account but then just end up back on the page where I have to create an account again.

21:01 <fruitytooty707> It never allows me to finish the setup and I wanted to see if someone knows about this issue?

21:33 <fruitytooty707> It appears to be the same behavior with Google as well. I am running the server on localhost. Would that be an issue for oauth?

21:39 <isd> OAuth should be able to work even on localhost; I've done that for dev setups on various projects before.

21:40 <fruitytooty707> Hmm, well I keep getting redirected back to http://127.0.0.1:6080/setup/user after authorizing my account...also there are no errors that show up in the log.

21:44 <isd> If it's directing you to an ip that's likely to be an issue. You need a wildcard domain for sandstorm to work anyway (though not because of OAuth)

21:52 <fruitytooty707> Same thing happens when it is configured as http://local.sandstorm.io:6080/

21:52 <fruitytooty707> it redirects to the local.sandstorm.io domain but never past the setup page