It could be that your SpiceDB Cluster is running w...
# spicedbc
corkrean
03/29/2023, 10:45 PMIt could be that your SpiceDB Cluster is running with TLS enabled and your client is using insecure mode. Could you double check that?
s
Syebaurgh
03/30/2023, 5:25 PMTLS was not enabled. Any idea what else it could be?
j
Joey
03/30/2023, 5:38 PMwhat call are you making?
s
Syebaurgh
03/30/2023, 6:24 PMchecking permissions
Syebaurgh
03/30/2023, 6:26 PMwith
CheckPermissionSyebaurgh
03/30/2023, 8:48 PM@Joey if you don't mind
j
Joey
03/30/2023, 8:49 PMits likely some sort of proxy or networking issue between wherever you're running the command and the SpiceDB cluster
Joey
03/30/2023, 8:49 PMeither that or SpiceDB never came up healthy
s
Syebaurgh
03/30/2023, 8:50 PMok, thank you
Syebaurgh
03/30/2023, 8:53 PMWhat do you mean by healthy. Is there a way to check the health of spicedb?
Syebaurgh
03/30/2023, 8:56 PMI don't see any such way in the authzed docs or with the spicedb command
Syebaurgh
03/31/2023, 8:15 PM@Joey
j
Joey
03/31/2023, 8:15 PMit should be shown in the logs on startup
Joey
03/31/2023, 8:15 PMhow are you running SpiceDB?
s
Syebaurgh
03/31/2023, 8:16 PMin a docker container from the authzed/spicedb image
j
Joey
03/31/2023, 8:16 PMcheck its logs
Joey
03/31/2023, 8:16 PMit should say whether it comes up healthy
s
Syebaurgh
03/31/2023, 8:17 PMgot it, thank you